Skip to content

Releases: giantswarm/kubectl-gs

v2.55.0

14 May 12:43
aca0bcd
Compare
Choose a tag to compare
Release v2.55.0 (#1326)

v2.54.0

14 May 07:24
5a30856
Compare
Choose a tag to compare

Changed

  • Default value for CAPA Node Pool rootVolumeSizeGB was decreased from 300 to 8.

v2.53.0

23 Apr 15:03
7e430bf
Compare
Choose a tag to compare

Changed

  • BREAKING kubectl gs template cluster for Cluster API provider Azure has been adapted to work with the values schema of cluster-azure v0.7.0.

v2.52.3

23 Apr 08:41
ffce8fb
Compare
Choose a tag to compare

Changed

  • Make error message actionable in case kubectl gs template cluster fails because the user did not log into, or point to, the management cluster
  • Support internal api URLs in kubectl gs login id token verification
  • Print a warning in case kubectl gs login id token verification fails but don't fail the command

v2.52.2

26 Mar 14:40
60efd06
Compare
Choose a tag to compare

Added

  • Add kubectl gs get nodepools for CAPA,CAPZ,CAPV,EKS and CAPVCD.
  • Add validation of ID token retrieved from OIDC provider during kubectl gs login

Changed

  • Errors during update checks no longer interrupt the command execution.
  • Fix authentication failure in case the browser sends multiple requests to the callback server during the login command execution

v2.52.1

01 Feb 09:20
5cd7f63
Compare
Choose a tag to compare

No significant changes compared to v2.52.0. This release was made to ensure the proper distribution to all channels, which failed with the last release.

v2.52.0

25 Jan 08:41
1f39c29
Compare
Choose a tag to compare

Added

  • Allow subnet generation customization for CAPA clusters.

v2.51.0

10 Jan 10:43
63dc338
Compare
Choose a tag to compare

Changed

  • Remove bastion section for generating CAPA cluster manifests.

v2.50.1

13 Dec 09:07
77dfbfc
Compare
Choose a tag to compare

Changed

  • Update values schema for generating EKS cluster.

v2.50.0

12 Dec 10:50
7c636cd
Compare
Choose a tag to compare

Breaking changes

  • kubectl gs template cluster: Either --name or new --generated-name parameter is now required for CAPI cluster names. We kept the CLI backward-compatible for vintage, so if none of these parameters is specified, the old default of generating a random name still applies and no error is thrown.