Fixed
- The
kubectl-gs logincommand no longer writes to the main kubeconfig file in case there are no changes in access tokens and/or the current context. - Using the
--contextflag will no longer modify the current context setting in kubeconfig.
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.--context flag will no longer modify the current context setting in kubeconfig.WARNING Please ensure you’re running kiam-app with App Version v2.5.1 or higher.
v1.4.5.WARNING Please ensure you’re running kiam-app with App Version v2.5.1 or higher.
This is necessary to allow efs-csi-driver to get the Identity Document from Instance Metadata Service.
You can verify this by describing kiam-agent DaemonSet and checking if --allow-route-regexp="/latest/*" is set.
v1.4.4.hostNetwork.n1-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.