Blue-Green Upgrade Configuration Not Applied Correctly

[vgupt312]

I am facing an issue with the blue-green upgrade strategy on Google Cloud Platform when applying the configuration using Terraform provider 5.11.0. Below is the relevant Terraform code and the corresponding configuration:

dynamic "blue_green_settings" {
for_each = lookup(local.node_pool_upgrade_settings, "strategy", "BLUE_GREEN") == "BLUE_GREEN" ? [1] : []
content {
node_pool_soak_duration = lookup(local.blue_green_settings, "node_pool_soak_duration", 1)
standard_rollout_policy {
batch_soak_duration = lookup(local.blue_green_settings, "batch_soak_duration", 1)
batch_percentage = lookup(local.blue_green_settings, "batch_node_count", null) == null ? lookup(local.blue_green_settings, "batch_percentage", 0.25) : null
batch_node_count = lookup(local.blue_green_settings, "batch_node_count", null)
}
}
}

Configuration:
strategy: "BLUE_GREEN"
blue_green_settings:
node_pool_soak_duration: 120s
batch_soak_duration: 300s
batch_percentage: 0.5

However, after applying this configuration, GCP is not considering the provided values and is displaying the following:
Upgrade strategy: Blue-green upgrade
Batch node count: 0
Batch soak duration: 0s
Nodepool soak duration: 3600s

It seems that the batch_node_count and batch_soak_duration are not being applied as expected.
Please investigate this issue and let me know if there's any misconfiguration or if there's a bug on the GCP side that needs attention.
However it is working fine when i am applying these settings using google command line.

I am attaching tfstate and other relevant documents.

Thanks,
Vivek

[vgupt312]

[edwardmedia]

@vgupt312 can you share the complete config and debug log? Please post the log at gist and share the link.

There are a few open issues. Can you see if they cover yours?

[vgupt312]

Terraform plan output:
https://gist.github.com/vgupt312/f7219b8120e1256134d1d1073e5c107e

[edwardmedia]

@vgupt312 the plan does not tell what went wrong. Do you have the log for apply? In order to help investigete, can you share a minimum config (without dynamic code) that can be used to repro the issue?

[edwardmedia]

@vgupt312 is this still an issue?

[edwardmedia]

@vgupt312 closing this assuming it is no longer an issue.

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.