Updates cluster commands to require an explicit flag if using a cluster
name instead of a cluster id. This could be a breaking change, as
previously you could pass either the id or name
Before this change, it was not possible to use the SSH command to
connect to machines provisioned with v2 provisioning. After this change
(and including the changes to Rancher), the CLI will use the new CAPI
client to get the SSH key and config from Rancher for v2 provisioned
machines.
A side effect of this change is the addition of the new `rancher
machines ls` command that lists all machines for the current cluster
context.
kubeconfig token will now be stored with the rest
of the rancher config rather than in the .cache
directory. The location of the config directory
can now be configured.
Problem:
Rancher supports enforcing apps versions but all app templates are shown
even if they are not compatable with the version of rancher running
Solution:
Add the rancherVersion filter when getting templates so only valid app
templates are shown
- Add subcommands for updating target projects
- Add subcommands for updating/listing members
- Add --member, --member-access-type option on install
- Add --role option on install/upgrade
- Add flag for showing role details in show-app command
Problem:
CLI asks to verify certs on login
No way to wait for a resource to be available
Solution:
Add a skip-verify flag to login
Add wait command to wait for a cluster to be in active state
Problem:
CLI asks to verify certs on login
No way to wait for a resource to be available
Solution:
Add a skip-verify flag to login
Add wait command to wait for a cluster to be in active state
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:
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:
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
Peter Matseykanets