You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci(e2e): run the Kubernetes e2e tests on an IPv6 kind cluster #5698
The Kubernetes e2e tests run only on IPv4 kind clusters. .github/actions/setup-e2e-kind/action.yml sets no ipFamily, so IPv6 regressions in the chart, gateway, or supervisor aren't caught.
Proposed Design
Add a Kubernetes e2e lane on a kind cluster with ipFamily: dual and IPv6 listed first in podSubnet and serviceSubnet, and install the chart with gateway.listenAddress and supervisor.listenAddress set to ::.
Acceptance Criteria
setup-e2e-kind can create an IPv6-primary dual-stack cluster.
A CI lane runs e2e:kubernetes and e2e:kubernetes:ha-rebalancing on that cluster.
Thanks for filing this. We're retiring the kind-based e2e setup (setup-e2e-kind, e2e/rust) in favor of the tmachine suites (#5281, #5297), so we'd like to get this IPv6 coverage there instead of adding a kind lane.
#5724 adds a tmachine environment, ubuntu-k3s-ipv6: a single-node k3s cluster that is dual-stack with IPv6 first in the pod and Service ranges, with gateway.listenAddress and supervisor.listenAddress set to ::. CI runs the conformance suite on it with the k3s-ha installer.
I checked it locally against your fixes: without #5669 OpenShell doesn't install, and without #5674 33 of 49 conformance tests fail on k3s-ha. With both, all 49 pass. #5696 (sandbox traffic to an IPv6 address) isn't covered by conformance, so it needs its own test.
Activity
matthewgrossman commentedon Nov 18, 2026
Thanks for filing this. We're retiring the kind-based e2e setup (
setup-e2e-kind,e2e/rust) in favor of the tmachine suites (#5281, #5297), so we'd like to get this IPv6 coverage there instead of adding a kind lane.#5724 adds a tmachine environment,
ubuntu-k3s-ipv6: a single-node k3s cluster that is dual-stack with IPv6 first in the pod and Service ranges, withgateway.listenAddressandsupervisor.listenAddressset to::. CI runs theconformancesuite on it with thek3s-hainstaller.I checked it locally against your fixes: without #5669 OpenShell doesn't install, and without #5674 33 of 49 conformance tests fail on
k3s-ha. With both, all 49 pass. #5696 (sandbox traffic to an IPv6 address) isn't covered by conformance, so it needs its own test.#5724 will close this issue when it merges.