gsctl v0.8.4

New features

• The gsctl create cluster command now offers the --aws-instance-type option. On AWS installations, this allows you to set the EC2 instance type for (all) worker nodes of a new cluster. The official instance type identifier, e. g. m3.large, is expected as value. (#138)

Note that not all instance types may be allowed on your installation. Pleas contact the Giant Swarm support team to help you find out which are the allowed types on your installation.

Minor changes

• The timeout for the API operations backing gsctl list clusters has been increased to reduce the likelyhood of an error (#136)

gsctl v0.8.3

Minor changes

• The output of gsctl list keypairs now also includes the columns CN (Common Name) and O (Organizations), which are relevant to role based access control (RBAC) (#132)

Bugfixes

• Issue #126 was closed. When calling the gsctl info command with an arbitrary endpoint defined via the -e|--endpoint flag, it was falsely printed that the user was logged in. (#133)

gsctl v0.8.0

New features

Endpoint management (#47, #120)

• The new concept of the "selected endpoint" eliminates the need to set an API endpoint with every command. You can now be logged in with several API endpoints at the same time. Endpoints can be switched easily.
• Use gsctl select endpoint <endpoint> to switch to a specific endpoint.
• Use gsctl list endpoint to show endpoints used and your login status.
• Use gsctl login <email> -e <endpoint> to add an endpoint and select it.
• Use gsctl logout to log out from the current endpoint.

See the according reference pages and Easily switching between environments for details.

Minor changes

• Binaries are now built using Go 1.9 (#123)
• gsctl list clusters output is now sorted by ID. The organization column has been moved to second position. (#125)
• Windows binaries are now signed (#119)
• create keypair and create kubeconfig: The --cn_prefix and --certificate_organizations flags have been renamed to --cn-prefix and --certificate-organizations (#118)

Bugfixes

• Fixed some cases where a token given via --auth-token has not been applied. (#92)

gsctl v0.7.1

Changes

The create keypair and create kubeconfig commands now support two additional optional flags:

cn_prefix and certificate_organizations for influencing the Subject of the issued certificate in order to control the rights of your issued certificates using Kubernetes RBAC Authorization.

See the reference pages for create keypair and create kubeconfig for more info.

gsctl v0.7.0

New features

• The gsctl scale cluster command has been added to change the number of worker nodes in a cluster. See the reference page for details. (#106)

Changes and Bugfixes

• We fixed a problem that prevented the Linux binary to be executed in a Docker container. As part of the fix, the Linux binary is no longer compiled statically. Instead it is linked against glibc. This means it can be run inside recent Ubuntu/Debian containers without modification. Using it inside an Alpine based image requires the addition of glibc. See this comment for an example. (#111)

• The gsctl version command now checks whether a newer version exists. The output has also changed to always show the build date. (#108)

• The output of the gsctl list clusters command has been fixed to always and in a line break. (#103)

gsctl v0.6.3

Changes

• gsctl now supports the use of a proxy server. If one of the environment variables HTTPS_PROXY or HTTP_PROXY is set, that value will be used as the proxy server URL. (#99)

gsctl v0.6.2

Changes

• We added support for API certificates signed by authorities that are not known to the operating system. CAs installed via the user's Mac OS keychain are now accepted. In addition, the environment variable GSCTL_CAFILE can be used to point gsctl to a CA bundle in PEM format. Alternatively, GSCTL_CAPATH can point to a directory containing CA certificates/bundles in PEM format. (https://github.com/giantswarm/gsctl/issues/96)

gsctl v0.6.1

Changes

• gsctl login can now be used when already logged in. This allows to switch accounts without the use explicit use of gsctl logout (https://github.com/giantswarm/gsctl/issues/22).
• gsctl info now prints which API endpoint is used (https://github.com/giantswarm/gsctl/issues/79).
• Better handling of several case when listing key pairs (https://github.com/giantswarm/gsctl/issues/71, https://github.com/giantswarm/gsctl/issues/72, https://github.com/giantswarm/gsctl/issues/64)
• Fixed a problem where the certificate and key file paths in kubectl configuration could become outdated after configuration migration (#63)

gsctl v0.6.0

Changes

• Configuration and obtained certificates are now stored in the $HOME/.config/gsctl directory (formerly $HOME/.gsctl), to reduce cluttering of a user's home directory. If you used a prior version of gsctl,
  your configuration and certificates are automatically moved to the new location.(https://github.com/giantswarm/gsctl/issues/39)
• We fixed a problem in gsctl create kubeconfig where the suggested command to switch to a context was wrong. Of course, the right command to use has to be kubectl config use-context <your-context>. (https://github.com/giantswarm/gsctl/issues/61)

gsctl v0.5.0

Changes

• The cluster-related functions have been updated to work with the latest API version (#53)
• The gsctl info command no longer outputs the two empty linkes about "Selected organization" and "Selected cluster" (#52)
• Some API requests now fail faster due to much shorter timeouts (#50)
• gsctl now sends a User-Agent header with gsctl/<version> with every API call (#50)
• Unexpected API responses are now handled in a unified way, hopefully returning all required information to track down a problem (#32)