v2.0.0

[gardenctl-v2]

✨ New Features

• [USER] Target command now has subcommands for each target kind. This improves working with the command, especially regarding command help (gardener/gardenctl-v2#95, @grolu)
• [USER] Generate gardenctl startup script that should be added to the users shell profile (gardener/gardenctl-v2#94, @holgerkoser)
• [USER] Implemented session isolation for the provider-env command. There should be no side effects across windows, tabs or panes. (gardener/gardenctl-v2#74, @holgerkoser)
• [USER] Added the config command. This command allows the user to add, modify, delete and show information about the configured garden landscapes. (gardener/gardenctl-v2#65, @holgerkoser)
• [USER] The information about the currently targeted cluster is no longer stored globally in the gardenctl home folder but in a temporary session directory. (gardener/gardenctl-v2#62, @holgerkoser)
• [USER] Added the kubectl-env command. This command generates a script that points KUBECONFIG to the currently targeted cluster for the specified shell. (gardener/gardenctl-v2#61, @holgerkoser)
• [USER] Added shoot control plane targeting. You can now switch to the control plane for a targeted cluster (gardener/gardenctl-v2#60, @grolu)
• [USER] Added klog flags like v (gardener/gardenctl-v2#57, @petersutter)
• [USER] Added pattern targeting. You can define regex patterns to match arbitrary values, like URLs to target a cluster (gardener/gardenctl-v2#44, @grolu)
• [USER] Added target view command (gardener/gardenctl-v2#40, @grolu)
• [USER] Added target unset command to unset targets or parts of it (gardener/gardenctl-v2#34, @grolu)
• [USER] Added auto-completion to --garden, --project, --seed and --shoot (gardener/gardenctl-v2#21, @xrstf)
• [USER] Added target command (gardener/gardenctl-v2#5, @xrstf)
• [USER] Added ssh command. You can optionally pass the node name as argument (gardener/gardenctl-v2#4, @xrstf)
  • Node name is provided : A remote shell to the node is opened automatically
  • Node name is not provided: The bastion is kept alive and the ssh command to open a remote shell to a node, together with the list of the shoot nodes is printed to stdout for your convenience. You can then run the ssh command on your own