Skip to content

docs: add a guide for IPv6-only kind clusters - #19

Open
ygao-g wants to merge 1 commit into
kind-ipv6-corednsfrom
docs-ipv6-local
Open

docs: add a guide for IPv6-only kind clusters#19
ygao-g wants to merge 1 commit into
kind-ipv6-corednsfrom
docs-ipv6-local

Conversation

@ygao-g

@ygao-g ygao-g commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Documents IP_FAMILY=ipv6, which has no docs today. Covers the Docker daemon
prerequisite, how to tell whether the host can route IPv6 without confusing
that with DNS, and the kubeconfig rewrite kubectl needs against a cluster
running in a Lima VM.

Split out of agent-substrate#1275 so the NAT64 half can be reviewed
on its own; this half describes only what the flag already does.

Based on agent-substrate#958 — without it an IPv6-only cluster's pods
resolve nothing, so the opening claim here is not true until that merges. The
base branch is kind-ipv6-coredns for that reason, and the diff is the new doc
plus one CONTRIBUTING.md link.

Part of agent-substrate#246.

🤖 Generated with Claude Code

@ygao-g
ygao-g force-pushed the docs-ipv6-local branch 3 times, most recently from e7f9827 to f42f322 Compare September 3, 2026 20:22
IP_FAMILY=ipv6 has no documentation, so the two things that reliably go
wrong get rediscovered every time: a Docker daemon with IPv6 off, and a
host that cannot route IPv6 at all. The second is usually measured with
`curl -6 <host>`, which cannot tell a resolver returning no AAAA apart
from a host with no route, and reports neither.

Also covers the kubeconfig rewrite kubectl needs when the cluster runs
in a Lima VM on macOS, where kind publishes the apiserver on [::1] and
Lima forwards that port to the host's 127.0.0.1.
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