ci: add an IPv6-only kind e2e job [DO NOT MERGE — needs #958 and #911] - #939
Draft
Yuan Gao (ygao-g) wants to merge 1 commit into
Draft
ci: add an IPv6-only kind e2e job [DO NOT MERGE — needs #958 and #911]#939Yuan 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
ci-kind-ipv6
branch
5 times, most recently
from
August 14, 2026 18:13
72285e4 to
68972e5
Compare
2 tasks
Yuan Gao (ygao-g)
changed the title
Yuan Gao (ygao-g)
force-pushed
the
ci-kind-ipv6
branch
from
August 17, 2026 18:11
68972e5 to
4363e8f
Compare
Yuan Gao (ygao-g)
force-pushed
the
ci-kind-ipv6
branch
from
August 19, 2026 01:23
4363e8f to
ef02488
Compare
Yuan Gao (ygao-g)
force-pushed
the
ci-kind-ipv6
branch
from
August 19, 2026 17:24
ef02488 to
748e841
Compare
Yuan Gao (ygao-g)
force-pushed
the
ci-kind-ipv6
branch
4 times, most recently
from
August 20, 2026 04:27
c9744a2 to
ba8d79e
Compare
No IPv6 coverage exists anywhere in CI, so nothing catches a change that works only because every address is IPv4. This builds a single-stack v6 kind cluster, installs, and runs the demo and networking suites, asserting the cluster really is single-stack first so a green run cannot be vacuous. Opt-in, not a gate. Label a pull request ci/ipv6 for a run, or dispatch it with a list of pull requests to merge onto main first. That second way is what lets this carry the workflow file alone: the changes it exists to exercise no longer have to ride along in the diff, and there is no branch to keep rebased. The label still has to be created upstream. Part of agent-substrate#246.
Yuan Gao (ygao-g)
force-pushed
the
ci-kind-ipv6
branch
from
August 20, 2026 16:43
ba8d79e to
af37e8b
Compare
Yuan Gao (ygao-g)
changed the title
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
1 participant
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.
Not for merging yet — it needs #958 and #911 in first. No IPv6 coverage exists anywhere in CI
today, so nothing catches a change that breaks IPv6-only, and the IPv6 work is a set of changes that
do little apart. This job builds a single-stack v6 kind cluster, does a full
--deploy-ate-systeminstall, and runs the
demoandnetworkingsuites, asserting the cluster really is single-stackfirst so a green run cannot be vacuous.
The branch is one workflow file. Dispatch it with a list of pull requests and it merges them onto
main in that order and runs the result; the stack lives for the length of the run and is never
pushed, which is what lets this carry no copy of the changes it exercises. Against main alone it
fails closed — the IPv6-only CoreDNS fix in #958 and the atenet admin bind in #911 both have to be
in before the install reaches anything, so until they land this would be a standing red rather than
a signal. After that it is mergeable as-is. It stays out of the
e2e-testgate either way, so itnever blocks a PR, and it still needs a maintainer to create the
ci/ipv6label before it can runon a pull request rather than only by dispatch. Part of #246.
🤖 Generated with Claude Code