gsctl v0.22.1

New features

• We introduce a new --sort/-s flag to the gsctl list clusters command to allow you to influence the output ordering. Sorting your tons of clusters by release, owner organization or creation date? Here you go.

Minor changes

• To get the version of gsctl, please use gsctl --version from now on. The old command gsctl version will show you a deprecation warning and will be removed at some point in the future.

gsctl v0.22.0

New features

• We've added support for cluster labels. Check out the Working with tenant cluster labels using gsctl documentation on this topic.

Minor changes

• The linux binaries from this release up now work on alpine linux.

gsctl v0.21.0

We've updated the Go version from v1.13.5 to v.14.2.

Minor changes

• The scale cluster command now supports atomic parameters for the worker nodes count. (#543)
• The list nodepools command now supports JSON output. (#545)

Bugfixes

• The list releases command would display some work in progress releases as deprecated. (#538)
• API errors with status code 400 are now handled gracefully. (#546)
• The ping command now displays a meaningful error when there's no endpoint selected. (#548)

gsctl v0.20.1

Bugfixes

• The authentication token is now redacted in the command-line header sent to the API (#537)

gsctl v0.20.0

New features

• The create nodepool command now supports requesting spot instances. See our reference docs for details. The list nodepools and show nodepool commands have also been updated to display information related to spot instances. (#528)
• The new environment variable GSCTL_AUTH_TOKEN can be used to specify an auth token to use, as an alternative to the global --auth-token flag especially in an automation context. The flag will take precedence when set. (#530)

Minor changes

• When creating a key pair with lifetime larger than 30 days with the create kubeconfig or create keypair commands, you will be prompted for confirmation. This prompt can be deactivated using the --force flag.
• The list clusters command has been updated to respect the --show-deleting flag also when -o json is used.
• The create kubeconfig and create keypair commands give a descriptive error message if you try to create a key pair for a cluster that is too young to have a working PKI backend. #532

gsctl v0.19.1

Minor changes

• When trying to create a key pair for a new cluster using the create kubeconfig or create keypair command, there is now more graceful handling for the case that the PKI backend to create the key pair is not ready yet. #532

gsctl v0.19.0

New features

• All commands that take a cluster ID, can now also work with the cluster name (#512, #513, #515, #509, #516, #517, #518, #519, #520, #521, #522, #523, #524). For more information, check the command's usage by executing it with the --help flag, or see https://docs.giantswarm.io/reference/gsctl/

gsctl v0.18.4

New features

• Deleting clusters can now be done using their name (ex: gsctl delete cluster "Testing cluster") (#509)

Minor changes

• Display an error message if there is no API endpoint selected (#508)

Bugfixes

• Setting an organization's credentials always fails with a 401 error (#510)
• Certain deprecated releases show up as in progress (#511)

gsctl v0.18.3

New features

• Shell completion for Bash now also allows to expand endpoint aliases. (#502)

Bugfixes

• A regression in the gsctl login command was fixed that prevented passing the email to the API call. (#507)

gsctl v0.18.2

New features

• There is now a command gsctl delete endpoint to remove an endpoint from the configuration. Use this command if you no longer want to work with an API endpoint. #501

Minor changes

• gsctl now warns you when trying to connect to an API endpoint via the HTTP protocol instead of HTTPS. #499

Bugfixes

• gsctl scale cluster and gsctl upgrade cluster have been fixed to work well with clusters using the v4 API (currently that's all Azure, all KVM, and AWS >= 10.0.0). #495 #497
• The gsctl delete nodepool command panicked when the argument did not have the expected syntax. This is fixed now and presents a helpful message about the syntax to use. #503