-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Remove master_auth fields from google_container_cluster resource #8032
Remove master_auth fields from google_container_cluster resource #8032
Comments
Note: This should only be removed if the lowest available GKE version has removed support for basic auth. |
At this point our tests for this feature are consistently failing with:
Previously they were failing with:
It's not exactly clear to me whether existing clusters might still be running 1.18, but it seems likely that creating new clusters now requires not using basic auth. |
So we're one more version away from being able to do this. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Upstream Kubernetes has deprecated and removed basic auth from kubernetes as of v1.19 . In the next major release of the provider,
master_auth
nested fields needs to be removed given that there are many breaking changes issues open against this resource.https://cloud.google.com/kubernetes-engine/docs/how-to/api-server-authentication#legacy-auth
rancher/rancher#28673
The text was updated successfully, but these errors were encountered: