Skip to content
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

container: fix node_config.kubelet_config updates in google_container_cluster #8238

Conversation

modular-magician
Copy link
Collaborator

This is still shy of a fix for updates for everything within node_config, and doesn't consolidate where we're updating the google_container_node_pool resource vs. the default-pool that can be created directly within google_container_cluster, but it does fix a subset of the fields that don't work, and also simplifies some of the code and consolidates some tests, so maybe still worth considering as another step in the right direction.

  • Fix updates for fields within node_config.kubelet_config where updates didn't function properly (basically all except for insecure_kubelet_readonly_port_enabled.
  • Consolidate test cases for items under node_config.kubelet_config with the one for node_config.kubelet_config.insecure_kubelet_readonly_port_enabled, including testing updates.

Part of hashicorp/terraform-provider-google#19225

Release Note Template for Downstream PRs (will be copied)

container: fixed `node_config.kubelet_config` updates in `google_container_cluster` resource

Derived from GoogleCloudPlatform/magic-modules#11697

…ner_cluster` (#11697)

[upstream:846050f21990e35de9b679c9dcac493204a02013]

Signed-off-by: Modular Magician <[email protected]>
@modular-magician modular-magician merged commit 1821aad into hashicorp:main Sep 20, 2024
4 checks passed
@modular-magician modular-magician deleted the downstream-pr-846050f21990e35de9b679c9dcac493204a02013 branch November 16, 2024 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant