You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
If an issue is assigned to the "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 to "hashibot", a community member has claimed the issue already.
New cluster using the above configuration creates fine however if you run plan again it tries to recreate because of the following:
node_pool.0.node_config.0.metadata.%: "1" => "0" (forces new resource)
node_pool.0.node_config.0.metadata.disable-legacy-endpoints: "true" => "" (forces new resource)
The problem with simply adding the metadata is when upgrading existing clusters, they all are forced new resources. There seems to be no way to get the old behavior that has an upgrade in place option.
Specifically I'm going from 1.11.5-gke.5 to 1.12.5-gke.10
Steps to Reproduce
terraform apply
2: Run plan again
The text was updated successfully, but these errors were encountered:
$ terraform version
Terraform v0.11.13
+ provider.google v1.20.0 ## OLD VERSION
+ provider.kubernetes v1.5.2
+ provider.null v1.0.0
+ provider.template v1.0.0
combined with a fresh GKE v1.12.5 cluster, I was able to add this to the google-container-cluster definition to make it work for producing new clusters and terraform plan for such a newly created cluster that does not do a recreated anymore.
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!
ghost
locked and limited conversation to collaborators
Apr 13, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Terraform v0.11.10
Affected Resource(s)
google_container_cluster
Terraform Configuration Files
Expected Behavior
New cluster using the above configuration creates fine however if you run plan again it tries to recreate because of the following:
The problem with simply adding the metadata is when upgrading existing clusters, they all are forced new resources. There seems to be no way to get the old behavior that has an upgrade in place option.
Specifically I'm going from 1.11.5-gke.5 to 1.12.5-gke.10
Steps to Reproduce
terraform apply
2: Run plan again
The text was updated successfully, but these errors were encountered: