-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Change container node pool defaults #8967
Change container node pool defaults #8967
Conversation
Hi there, I'm the Modular magician. I've detected the following information about your changes: Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. If you intend to make this change you will need to wait for a major release window. An Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 3 files changed, 7 insertions(+), 7 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 42 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccContainerCluster_withNodeConfigReservationAffinity|TestAccContainerCluster_withConfidentialNodes|TestAccContainerCluster_withILBSubsetting|TestAccContainerNodePool_withHostMaintenancePolicy|TestAccContainerNodePool_withConfidentialNodes|TestAccContainerNodePool_threadsPerCore|TestAccContainerCluster_withSoleTenantGroup|TestAccContainerNodePool_012_ConfigModeAttr|TestAccContainerNodePool_customPlacementPolicy|TestAccContainerCluster_withNodeConfigReservationAffinitySpecific|TestAccContainerNodePool_withSoleTenantConfig|TestAccContainerNodePool_withLinuxNodeConfig|TestAccContainerNodePool_shieldedInstanceConfig|TestAccContainerNodePool_EmptyGuestAccelerator|TestAccContainerNodePool_withNodeConfigScopeAlias|TestAccContainerNodePool_withManagement|TestAccContainerNodePool_withGPU|TestAccContainerNodePool_withMultiNicNetworkConfig|TestAccContainerNodePool_withEnablePrivateNodesToggle|TestAccContainerNodePool_withNodeConfig|TestAccContainerNodePool_withKubeletConfig|TestAccContainerNodePool_withReservationAffinitySpecific|TestAccContainerNodePool_withWorkloadIdentityConfig|TestAccContainerNodePool_withReservationAffinity|TestAccContainerNodePool_withSandboxConfig|TestAccContainerCluster_customPlacementPolicy|TestAccContainerNodePool_gcfsConfig|TestAccContainerNodePool_compactPlacement|TestAccContainerCluster_withNodeConfigShieldedInstanceConfig|TestAccContainerCluster_withNodeConfigScopeAlias|TestAccContainerNodePool_gvnic|TestAccContainerNodePool_ephemeralStorageLocalSsdConfig|TestAccContainerNodePool_localNvmeSsdBlockConfig|TestAccContainerCluster_withNodeConfig|TestAccContainerNodePool_withNetworkConfig|TestAccContainerCluster_withNodePoolDefaults|TestAccContainerCluster_withNodePoolNodeConfig|TestAccContainerNodePool_ephemeralStorageConfig|TestAccContainerCluster_backend|TestAccContainerCluster_withBootDiskKmsKey|TestAccContainerCluster_withSandboxConfig|TestAccContainerCluster_withWorkloadMetadataConfig |
Rerun these tests in REPLAYING mode to catch issues
|
e18b441
to
685e573
Compare
Hi there, I'm the Modular magician. I've detected the following information about your changes: Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. If you intend to make this change you will need to wait for a major release window. An Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 4 files changed, 11 insertions(+), 7 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccContainerNodePool_withKubeletConfig|TestAccVertexAIIndexEndpoint_updated |
|
685e573
to
b1c8ef0
Compare
Hi there, I'm the Modular magician. I've detected the following information about your changes: Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. If you intend to make this change you will need to wait for a major release window. An Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 4 files changed, 8 insertions(+), 7 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccAlloydbInstance_createInstanceWithNetworkConfigAndAllocatedIPRange|TestAccContainerNodePool_fastSocket|TestAccVertexAIIndexEndpoint_updated |
Rerun these tests in REPLAYING mode to catch issues
|
@@ -2614,6 +2614,7 @@ resource "google_container_node_pool" "with_kubelet_config" { | |||
"https://www.googleapis.com/auth/logging.write", | |||
"https://www.googleapis.com/auth/monitoring", | |||
] | |||
logging_variant = "DEFAULT" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume we have a bunch of tests where this is not set, so we don't need to add one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the majority of tests do not have this set
7bef6de
into
GoogleCloudPlatform:FEATURE-BRANCH-major-release-5.0.0
fixes hashicorp/terraform-provider-google#6236
fixes hashicorp/terraform-provider-google#13706
both auto repair and auto upgrade default to true according to these docs and verified in testing
https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair
https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-upgrades
upgrade guide: #8969
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
in the generated providers to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)