[gardenctl-v2]

⚠️ Breaking Changes

• [USER] Removed wrongfully added --output flag for the following commands. Setting the flag did not have any effect previously but will now result in an error: (gardener/gardenctl-v2#305, @petersutter)
  • target
  • target garden
  • target project
  • target seed
  • target shoot
  • target control-plane

✨ New Features

• [USER] ssh: reuse bastion, e.g. gardenctl ssh --keep-bastion --bastion-name cli-xxxxxxxx --public-key-file /path/to/ssh/key.pub --private-key-file /path/to/ssh/key (gardener/gardenctl-v2#283, @petersutter)
  • --bastion-name flag was added. If a bastion with this name doesn't exist, it will be created. If it does exist, the provided public SSH key must match the one used during the bastion's creation
  • --private-key-file flag was added. It must be provided alongside the --public-key-file flag if you want to use a custom keypair. If not provided, gardenctl will either generate a temporary keypair or rely on the user's SSH agent for an available private key.
• [USER] ssh: Use the --bastion-host and --bastion-port flags to customize the bastion host and port for the SSH client command, respectively. These flags are useful when you need to specify an alternative host and port for SSH port forwarding scenarios. (gardener/gardenctl-v2#284, @petersutter)
  • --bastion-host: Specify a custom hostname or IP address for the bastion used in the SSH client command. If not provided, the address will be automatically determined.
  • --bastion-port: Set the SSH port of the bastion used for the SSH client command. By default, this value is set to port 22.
• [USER] ssh: Use the --bastion-user-known-hosts-file flag to specify a custom known hosts file for the SSH connection to the bastion host. This is useful when the bastion host IP is reused, which can lead to a failed remote host key verification if there is an existing entry for the same IP but from a previous (old) bastion. (gardener/gardenctl-v2#285, @petersutter)
• [USER] The target view command (alias gtv) now also considers the target flags (gardener/gardenctl-v2#289, @petersutter)
• [USER] provider-env: You can now control the output format using --output flag. The data that is typically passed to the templating engine for generating provider-env scripts is instead output in the specified format. Usage: gardenctl provider-env -oyaml (gardener/gardenctl-v2#298, @petersutter)
• [USER] Added resolve command in order to resolve garden, seed, project or shoot for the current target. This command is particularly useful when you need to understand which shoot the current target translates to, regardless of whether a seed or a shoot is targeted. (gardener/gardenctl-v2#306, @petersutter)
• [USER] ssh: Added flag --confirm-access-restriction. Using this flag bypasses the need for confirmation of any access restrictions. Set this flag only if you are fully aware of the access restrictions. (gardener/gardenctl-v2#309, @petersutter)

🐛 Bug Fixes

• [USER] Removed unnecessary newline for yaml output (gardener/gardenctl-v2#297, @petersutter)

🏃 Others

• [USER] ssh: the command that is printed to stdout is now shell-escaped (gardener/gardenctl-v2#279, @petersutter)
• [USER] provider-env: ⚠️ The --force is now deprecated. Use --confirm-access-restriction flag instead. The --force flag will eventually be removed in a future version. (gardener/gardenctl-v2#309, @petersutter)