-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev] Use gke-gcloud-auth-plugin for kubectl #10687
Conversation
started the job as gitpod-build-af-add-gcloud-auth.1 because the annotations in the pull request description changed |
started the job as gitpod-build-af-add-gcloud-auth.3 because the annotations in the pull request description changed |
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-af-add-gcloud-auth.4 |
/werft run 👍 started the job as gitpod-build-af-add-gcloud-auth.5 |
Start using the kubectl auth plugin for GKE. See https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
0251a63
to
95d08d6
Compare
|
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-af-add-gcloud-auth.8 |
started the job as gitpod-build-af-add-gcloud-auth.9 because the annotations in the pull request description changed |
started the job as gitpod-build-af-add-gcloud-auth.10 because the annotations in the pull request description changed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Start using the kubectl auth plugin for GKE.
See https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
Without this change, attempting to connect to eg the staging cluster with
kubectl
would print this warning before every command:By switching to use the auth plugin this warning goes away.
Related Issue(s)
How to test
Gitpod
button for this PR.gcloud auth login
in the new workspace and follow the instructions.gcloud container clusters get-credentials ...
kubectl get pods
There should be no warning printed about authentication.
Release Notes