We're running both GKE clusters and on-prem k8s clusters. We've discovered that the kubectl command installed via the kubectl package in the apt repository at https://packages.cloud.google.com/apt reaches out to a cluster - I think the current default context - for every command. The Release Notes have this:
https://cloud.google.com/sdk/docs/release-notes#kubernetes_engine_170
Update Google Container Engine's kubectl so that it now first attempts to match the API server version. If successful, the kubectl will delegate to the matching version of kubectl.
However, this is even done for commands like "kubectl completion bash", which we tell people to put in their ~/.bashrc (as "source <(kubectl completion bash)".
If their current context is not a GKE cluster when they start a new shell (new terminal window, ssh'ing in, etc) then it attempts to authenticate to the on-prem cluster, which for us involves OIDC login through a browser, which is disruptive at best and can hang the login shell if it fails at worst.
Is there a way to disable this in the Google kubectl package?
LinkedIn
Twitter
