-
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
google_container_cluster with google_container_node_pool update causes 400 badRequest #3035
Comments
I was able to work around this issue via
|
Signed-off-by: Modular Magician <[email protected]>
Signed-off-by: Modular Magician <[email protected]>
Signed-off-by: Modular Magician <[email protected]>
This is due to the underlying API I think. Some operations are impossible on node-less clusters, which happens if your final node pool is deleted. Unfortunately, there isn't anything that can be done in the provider to mitigate this behaviour. Apply ordering is chosen by Terraform Core. |
Wasn't able to reproduce it using terraform 1.6.5. Here's what I attempted: Code tested:
Steps followed:
Output log
|
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Full logs: https://gist.github.com/jkamenik/4fdeff4cb4341358f172910a1cfff3fd
Panic Output
N/A
Expected Behavior
Update the node-pool before updating the main cluster.
Actual Behavior
Both the node-pool and cluster are updated at the same time, and as soon as the node-pool is deleted then the main cluster updates with a 400 error.
Steps to Reproduce
terraform apply
terraform apply
Important Factoids
References
b/299442591
The text was updated successfully, but these errors were encountered: