Skip to content

ci(e2e): run conformance on an IPv6-first k3s cluster - #5724

Draft
matthewgrossman wants to merge 8 commits into
mainfrom
test/5698-k3s-ipv6-environment/matthewgrossman
Draft

matthewgrossman wants to merge 8 commits into
mainfrom
test/5698-k3s-ipv6-environment/matthewgrossman

Conversation

@matthewgrossman

@matthewgrossman matthewgrossman commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Summary

Add a tmachine environment, ubuntu-k3s-ipv6, with a dual-stack K3s cluster that uses IPv6 first, and run the conformance suite on it with the k3s-ha installer. This covers OpenShell on IPv6 Kubernetes without adding a kind-based lane.

Related Issue

Closes #5698

Changes

  • QEMU user networking gives guests fd00:10::/64 instead of its default fec0::/64. Linux ranks the site-local fec0:: below other addresses, so on a dual-stack guest the node sent traffic to IPv6 Services from flannel's address and never got the reply.
  • New ipv6 feature environment on the ubuntu-k3s base (k3s-ipv6.yaml). It configures K3s with IPv6-first pod and Service ranges, checks the node can reach a pod through an IPv6 Service, and resets the cluster before the disk is cached.
  • The environment writes /etc/openshell-test/helm-values.yaml (gateway and supervisor listenAddress: "::"). The k3s and k3s-ha installers apply that file last when it exists.
  • The installers accept an IPv6 gateway ClusterIP and bracket it in the client endpoint.
  • The K3s reset tasks move to k3s-reset.yaml so both setup playbooks share them. ubuntu-k3s is unchanged.
  • One CI row: conformance on ubuntu-k3s-ipv6 with k3s-ha.
  • TESTING.md documents the environment Helm values file.

Testing

Ran locally on an arm64 Mac:

Sandbox egress to an IPv6 address (#5696) is not covered by conformance; it needs a separate test.

  • Checks appropriate to the affected code and behavior pass
  • Unit tests added/updated (if applicable)
  • E2E tests added/updated (if applicable)

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)

QEMU user networking defaults to the site-local fec0::/64, which Linux ranks below any global address. On a dual-stack K3s guest the node then sends to IPv6 Services from flannel's address and never gets the reply.

Signed-off-by: Matthew Grossman <[email protected]>
…lues in the k3s installers

Signed-off-by: Matthew Grossman <[email protected]>
@copy-pr-bot

copy-pr-bot Bot commented Nov 18, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@github-actions github-actions Bot added the state:accepted A maintainer decided OpenShell should pursue this issue label Nov 18, 2026
@matthewgrossman

Copy link
Copy Markdown
Member Author

/ok to test 9073847

@matthewgrossman matthewgrossman added the test:e2e Requires end-to-end coverage label Nov 18, 2026
@github-actions

Copy link
Copy Markdown

Label test:e2e applied for 9073847. Open Branch E2E Checks, find the run for commit 9073847, and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway, sandbox, and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.

…eway address

Create an empty environment Helm values file when the environment has none, so the Helm command is a plain list. Name the gateway IP and port before bracketing an IPv6 address.

Signed-off-by: Matthew Grossman <[email protected]>
@matthewgrossman

Copy link
Copy Markdown
Member Author

/ok to test e30f2e2

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:accepted A maintainer decided OpenShell should pursue this issue test:e2e Requires end-to-end coverage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci(e2e): run the Kubernetes e2e tests on an IPv6 kind cluster

1 participant