@taylorbot taylorbot released this Dec 10, 2018 · 3 commits to master since this release

Assets 6

Minor changes

  • The gsctl version command now uses a different URL to detect which is the latest gsctl version. The URL used by gsctl until 0.14.3 will only be updated one more time, to inform about this release being available.
  • The single-sign-on HTML code has been improved for readability.

@teemow teemow released this Nov 23, 2018 · 9 commits to master since this release

Assets 6

Minor changes

The gsctl show cluster command now also shows a list of availability zones the cluster is running in. The availability zones get selected randomly.

Note: On AWS the names of availability zones are randomized per account. So eu-west-1a in the clusters account can be any other availability zone in a different account

Find more information in our docs: https://docs.giantswarm.io/basics/multiaz/

@teemow teemow released this Nov 22, 2018 · 11 commits to master since this release

Assets 6

New features

The gsctl create cluster command now has a new flag --availability-zones. The flag specifies the number of availability zone a cluster should have. The default is 1 and you can only specify more than one availability zones together with a Giant Swarm provider and release version that supports multiple availability zones.

Minor changes

We've increased the timeout for API calls. This was made for clusters that had lots of keypairs. In the mean time we also improved the keypair listing performance so there are no more API calls that make you wait for 20 seconds.

@marians marians released this Oct 26, 2018 · 15 commits to master since this release

Assets 6

Minor changes

  • The gsctl show cluster command now shows provider credentials for AWS or Azure in case the cluster is running in a different account/subscription than the default one. That is the case when provider credentials have been set for the organization using update organization set-credentials. (#308)

Bugfixes

  • The gsctl upgrade cluster command would select the next version, from the perspective of the cluster's current version, as the target to upgrade to, without checking whether that version is active or deprecated. This prevented an upgrade on the API side. Now the next active release is selected. (#310)

@marians marians released this Oct 26, 2018 · 18 commits to master since this release

Assets 6

New features

  • The new command gsctl upgrade cluster allows to upgrade a cluster to the next release version. Please read the upgrade documentation before use. (#192)

Minor changes

  • Binaries are now built using Go v1.11.1.
  • We introduced validation of the --cn-prefix flag in the create kubeconfig and create keypair commands to help users using the allowed character set only. (#306, #307)

@teemow teemow released this Oct 5, 2018 · 28 commits to master since this release

Assets 6

New features

  • The gsctl list releases command has changed to a more compact table. A new command called gsctl show release shows more details about a release. (#300)

Minor changes

  • The deprecated and unused --kubernetes-version parameter was removed from gsctl create cluster. (#299)

@marians marians released this Sep 12, 2018 · 33 commits to master since this release

Assets 6

New features

  • The update organization set-credentials command has been added to allow setting BYOC (bring your own cloud) credentials. See the reference documentation for details. (#291)

Minor changes

  • gsctl login in combination with the -v / --verbose flag will no longer print the password. (#293)

@marians marians released this Aug 20, 2018 · 38 commits to master since this release

Assets 6

Minor changes

  • The gsctl show cluster command, when executed against an AWS or Azure installation, no longer prints information regarding the storage in worker nodes. This information didn't have any practical value, as it could not be used by users. This is likely to change at some point in the future and the information will be made available again.

@marians marians released this Aug 16, 2018 · 41 commits to master since this release

Assets 6

Minor changes

  • SSO sessions are now automatically extended by the use of a refresh token. SSO authentication is currently only available to Giant Swarm staff members.

@marians marians released this Aug 1, 2018 · 50 commits to master since this release

Assets 6

Under the hood

This release focuses on a major change in the client library used to communicate with the Giant Swarm API. As one effect, all uses of v1 API endpoints have been eliminated. All API communication now uses v4 endpoints.

Minor changes

  • When listing key pairs with gsctl list keypairs, key pairs that expire within the next 24 hours are highlighted in yellow. (#274)
  • In create kubeconfig and create keypair, the handling of high TTL values has been improved. Note: For security reasons, we do not recommend creating key pairs with a TTL of several months or years. (#275).
  • The output of the gsctl ping command has changed slightly to avoid fractions of milliseconds. (#277)