Fixed
- Fix
update cluster
command when scheduling an upgrade for a Cluster when the Cluster CR had no previous annotations.
update cluster
command when scheduling an upgrade for a Cluster when the Cluster CR had no previous annotations.cert-operator
version 0.0.0
is used for client certificate creation in login
command to avoid timeouts.kubectl-gs login
command no longer writes to the main kubeconfig file in case there are no changes in access tokens and/or the current context. Also setting the --context
flag will no longer affect the current context (current-context
in kubeconfig) #949n1-standard-4
as default instance types for CAPG worker nodes.login
command to prevent updates of the main kubeconfig file in case there are no changes in access tokens and/or the current context, or if the current context is provided via override (e.g. by using the --context
flag).kubectl gs template nodepool
command for Cluster API (CAPI) based workload Clusters.get nodepools
when node pool is lacking the release version label.github.com/giantswarm/kubectl-gs/v2
.cluster-values
configmap when templating the default-apps-aws
app.login
command where the issuer
URL was used instead of the server
address in login retry attempt.--gcp-machine-deployment-sa-email
and --gcp-machine-deployment-sa-scopes
to template cluster
that specify a Google Cloud Platform service account and its scope to a cluster’s machine deploymentskubectl gs login
command to ensure that it writes to the main kubeconfig file only in case there are actual changes in the content of the file.This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.