-
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
GKE cluster and node pools fail when using valid Kubernetes labels #6003
GKE cluster and node pools fail when using valid Kubernetes labels #6003
Comments
@clebio GKE API is not allowing to set Kubernetes name space labels for the cluster nodeconfig. I am able set custom namespace labels for the node config
Please let us knows if it helps |
This should be documented on the
|
yes, we will update the doc. resource should document that |
Confirmed in my reproduction code above that something like |
I created a GKE feature request to allow node-role.kubernetes.io labels over on the Google issue tracker. Up vote and/or add your two cents if you would like to see this implemented: |
can't believe a doc update took 6 months and haven't completed |
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 👉 hashibot-feedback@hashicorp.com. 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
Affected Resource(s)
Terraform Configuration Files
Debug Output
Sorry, I'm not comfortable providing Terraform debug logs without first auditing to remove private identifiers (actual project ID, e.g.).
Panic Output
n/a
Expected Behavior
apply
should not fail.Actual Behavior
Terraform
apply
fails with (reproduced for both node pool and cluster):Steps to Reproduce
terraform apply
Important Factoids
Applying the same Kubernetes labels works via
kubectl
:References
None that I have found are directly related.
The text was updated successfully, but these errors were encountered: