Releases: giantswarm/kubectl-gs
Releases · giantswarm/kubectl-gs
v2.41.0
v2.40.0
Added
- Add
--login-timeout
flag to control the time period of OIDC login timeout - Add experimental support for templating
cluster-eks
with providereks
.
Changed
- Graceful failure of the
login
command in case workload cluster API is not known - Improved error message after login timeout
v2.39.0
Breaking changes
- Add minimal support for templating CAPZ clusters by command line parameters. This removes
--cluster-config
and--default-app-config
parameters which required handcrafted YAML input. It leaves one consistent templating option for CAPI products (kubectl gs template cluster --provider ... --other-params
).
v2.38.0
Changed
Fixed
- Sanitize file passed as inputs data for config maps by stripping spaces from the right end of the lines.
- This makes the output to use proper multi-line strings for the embedded YAML content by working around a bug in
sig.k8s.io/yam@v1.3.0
- This makes the output to use proper multi-line strings for the embedded YAML content by working around a bug in
v2.37.0
v2.36.1
v2.36.0
v2.35.0
v2.34.1
Fixed
kubectl gs template cluster
now by default creates a node pool with the namenodepool0
, instead ofmachine-pool0
, as the latter is no longer valid according to the cluster-aws schema as of v0.24.0.
v2.34.0
Added
cluster template
supports a generic way to templateCAPI
based clusters where all the input parameters are given asvalues.yaml
from the correspondingcluster
anddefault-apps
chart.- CAPZ: removed unmaintained
CAPZ
implementation and switched to the generic templating implementation.
Changed
kubectl gs template cluster
for Cluster API provider AWS (--provider capa
) has been adapted to work with the values schema of cluster-aws v0.28.0.