tests: add minimal_gce_ipv6 integration test - #18769
Merged
kubernetes-prow[bot] merged 1 commit intoSep 1, 2026
Merged
Conversation
Adds a golden integration test for an IPv6 GCE cluster with private topology, covering the dual-stack subnet configuration (stackType IPV4_IPV6, ipv6AccessType EXTERNAL) and the CloudNAT router. The scenario uses networking.cni rather than kindnet because kindnet on GCE uses the IP-alias path, where performNetworkAssignmentsIPAliases currently overwrites nonMasqueradeCIDR (::/0) with 10.0.0.0/8, silently turning the cluster back into IPv4.
kubernetes-prow
Bot
added
kind/cleanup
hakman
approved these changes
Sep 1, 2026
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes-prow
Bot
added
the
approved
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Adds a golden integration test (
TestMinimalGCEIPv6/tests/integration/update_cluster/minimal_gce_ipv6) for an IPv6 GCE cluster with private topology. The golden terraform output locks in the current GCE IPv6 rendering:stack_type = "IPV4_IPV6",ipv6_access_type = "EXTERNAL") — pods/services IPv6-only, VMs dual-stackserviceClusterIPRangedefaultinggoogle_compute_router_nat) — this is the resource that GCE: enable NAT64 for IPv6-only clusters #18520 extends with NAT64, so that PR (and future GCE IPv6 work on Support for IPv6 only cluster on GCE #17840) will show up as a reviewable golden diff hereWhy networking.cni rather than kindnet
While writing this I found that kindnet on GCE takes the IP-alias path (
gce.UsesIPAliases), whereperformNetworkAssignmentsIPAliasesunconditionally overwritesnonMasqueradeCIDR: ::/0with10.0.0.0/8when pod/service CIDRs aren't preset — silently turning an IPv6 cluster spec back into an IPv4 cluster. Until that's fixed, a kindnet-based IPv6 scenario would just render an IPv4 cluster, so this test usesnetworking.cni(matchingminimal_gce_private). I'll file the IP-alias/IPv6 issue separately.Part of #17840
/kind cleanup
/area provider/gcp