Releases: giantswarm/kubectl-gs
Releases · giantswarm/kubectl-gs
v2.55.0
v2.54.0
Changed
- Default value for CAPA Node Pool
rootVolumeSizeGB
was decreased from300
to8
.
v2.53.0
Changed
- BREAKING
kubectl gs template cluster
for Cluster API provider Azure has been adapted to work with the values schema ofcluster-azure
v0.7.0.
v2.52.3
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
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
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
Added
- Allow subnet generation customization for CAPA clusters.
v2.51.0
Changed
- Remove bastion section for generating CAPA cluster manifests.
v2.50.1
Changed
- Update values schema for generating EKS cluster.
v2.50.0
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.