-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
setting node_config on autopilot clusters should not be allowed #8863
setting node_config on autopilot clusters should not be allowed #8863
Comments
I don't see Node config is pre-configured for AutoPilot mode as per the docs https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview. It looks to me provider is inline with the specs. Please let us know if you see otherwise . |
@venkykuberan the problem is, when you do specify it all of your settings will be overridden and your clusters will be recreated. |
I could successfully create a cluster with autopilot and node_config included, so that seems not to be a problem, what I am struggling with it is how to pass a service account different from the default one and oauth scopes for the node, I used the node_config block for that but it is not working, it is ignored, cluster_autoscaling is another way to pass this info but this setting is conflicting with autopilot.
|
Huh, I'm not too familiar with the autopilot mode or GKE itself. From what I'm looking at on the docs page: https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview it looks like authentication is handled through workload identity. I'm not sure how we would set the scopes like in that gcloud command, but I'm pretty sure that setting it on the autoscaling block won't be what you want. Terraform is using the REST API: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters so there would need to be a way to set that field through the API for us to be able to enable it. Can you track down how that service account is being used in the API calls through gcloud? |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
v0.14.7
Affected Resource(s)
Terraform Configuration Files
The text was updated successfully, but these errors were encountered: