Problem:
An app creates a namespace to deploy into and depending on the system it
might not be ready when attempting to install the app
Solution:
Poll the namespace to ensure it's active before proceeding with
installing the app
Problem:
Apps of the same name deploy into the same namespace. This fails when a
namespace is owned by another project
Solution:
Apps should be deployed into a unique namespace unless specified
otherwise.
Add a flag to specify the namespace
Create a namespace with a random suffix to deploy the app into if
namespace is not specified
Update deletes to allow passing in multiple names/IDs for the same resource.
Update ls of resources to accept --quiet to allow passing to delete
Update arg checking to stop being an error and instead show --help for the command/subcommand
Problem:
When creating the master client, three other clients are needed which
requires multiple calls to the rancher server. This is done synchronously
and causes large delays before the command is actually run
Solution:
Build the clients async to speed up the time it takes to build the
master client
Problem:
SSH command does not accept a user or allow passing through of commands
Solution:
Add support for -l flag as well as <user>@<node> syntax
Pass through all following args to SSH
Problem:
Specifying a cluster on project create and a project using ps required
an ID
Solution:
Use the lookup by name
Update the description of the ps command
Problem:
Some rancher servers are running SSL certs that fail validation so an
existing k8s cluster would not import through a standard kubectl call
Solution:
Output a second option using curl to download the file and pass it to
kubectl thus avoiding the SSL check
Problem:
Unable to do any members actions with clusters and projects
Solution:
Add ability to add and remove members from clusters and projects
rancher project add-member-role --role <a> --role <b> <user>
Add new subcommands to list available roles for the cluster/project
rancher project list-roles
Add new subcommand to list current members/roles in a cluster/project
rancher project list-members
Problem:
kubectl is using the users kubeconfig on the system and not the one
specific to the cluster
Solution:
kubectl now pulls the clusters kubeconfig and uses that to run kubectl
commands
Problem:
Cluster does not match the ui
Solution:
Update ls layout to match ui
Add new column for currently focused cluster
Add options from the UI for creation of cluster
Problem:
When logging in a previous config would be used and if the cluster was
removed an error would occur
Solution:
Previous configs are no longer used for login
