hack: make the kind cluster's IP family configurable - #827
Closed
Yuan Gao (ygao-g) wants to merge 1 commit into
Closed
hack: make the kind cluster's IP family configurable#827Yuan Gao (ygao-g) wants to merge 1 commit into
Yuan Gao (ygao-g) wants to merge 1 commit into
Conversation
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
2 times, most recently
from
August 10, 2026 20:42
7138ea3 to
b174fd2
Compare
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
from
August 10, 2026 21:39
b174fd2 to
cac4c9f
Compare
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
from
August 10, 2026 21:55
a4322ae to
ae2045a
Compare
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
from
August 10, 2026 22:24
ae2045a to
dff80c5
Compare
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
from
August 10, 2026 23:14
dff80c5 to
690728f
Compare
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
4 times, most recently
from
August 11, 2026 02:42
35b7b13 to
1c3a9b7
Compare
Yuan Gao (ygao-g)
marked this pull request as ready for review
August 11, 2026 02:50
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
3 times, most recently
from
August 11, 2026 15:54
00c7e32 to
391a903
Compare
Collaborator
Author
KIND_IP_FAMILY selects ipv4, ipv6 or dual and becomes networking.ipFamily, leaving kind's per-family subnet defaults alone. The script also recreates a pre-IPv6 "kind" Docker network, fails fast if the daemon has IPv6 off, sets proxy_ndp alongside proxy_arp for gVisor pod-to-pod traffic, and repoints an ipv6 kubeconfig from [::1] at localhost so a client outside the Docker host can still reach the apiserver. Tested on kind with all three families using the new hack/verify-kind-networking.sh, which checks node InternalIPs, ClusterIPs, pod IPs, pod-to-pod, CoreDNS, and a pull through the local registry. Pod IPs, pod-to-pod and Service allocation run once per requested family rather than only the primary one, on separate ports so a single [::] socket cannot serve IPv4 through v4-mapped addresses and mask the v4 path.
Yuan Gao (ygao-g)
force-pushed
the
kind-ip-family-core
branch
from
August 11, 2026 18:38
391a903 to
7e6c3c6
Compare
Collaborator
Author
|
Closing this one — the thread here is all self-review noise from iterating on the script, with no reviewer feedback to carry over. Refiled as #877 with the same commit for a clean read. |
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
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.
KIND_IP_FAMILYselectsipv4,dual, oripv6and passes this through to kind. To prevent insidious failures like pods stuck inContainerCreating, the script now drops old Docker networks to force IPv6 recreation if needed, validates the daemon's IPv6 support up-front, and enablesproxy_ndp(alongsideproxy_arp) to properly support gVisor loopback pod-to-pod networking across IPv6 nodes.The networking setup is fully validated using the newly added
hack/verify-kind-networking.sh, which confirms reliable IPv6 distribution across Node IPs, Service ClusterIPs, Pod IPs, Registry configurations, and CoreDNS lookups.