Repository navigation
Conversation
Actors only got the IPv4 /30, so an IPv6-only cluster could not run them and a dual-stack one gave them no IPv6 egress. The sandbox now follows the worker pod's IP families: IPv4 169.254.17.0/30, IPv6 fd00:a7e:17::/126, or both. Each family gets its own nftables table, /etc/hosts entry and wakeup probe address. Dialing a family the sandbox lacks fails with ENETUNREACH. Both workers pass the families to actornet, and the e2e tests no longer assume IPv4 addresses. Signed-off-by: steigr <me@stei.gr>
steigr
force-pushed
the
ipv6/actor-networking
branch
from
November 19, 2026 11:28
1956199 to
a04f789
Compare
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.
Actors only get the IPv4 link-local /30, so they cannot run on an IPv6-only
cluster, and on a dual-stack cluster they have no IPv6 egress.
The actor sandbox now follows the worker pod's IP families: IPv4
169.254.17.0/30, IPv6 fd00:a7e:17::/126, or both. Each family gets its own
nftables table, /etc/hosts entry and wakeup probe address. A dial to a family
the sandbox lacks fails with ENETUNREACH. Both the gVisor and microVM workers
pass the families to actornet.
The diff is about 1,240 lines, 60% of them tests. Every part depends on the
new actornet.Families API or on actors having IPv6, so it is one commit.
Part of IPv6 support: #182
Known gaps:
where the Jupyter demo image lives.
Testing: unit tests, including the root-gated ones. The full e2e suite on kind
in a Lima VM on arm64 macOS, for ipv4, ipv6 and dual, on gVisor and microVM,
with both the Envoy and agentgateway dataplanes. The IPv6-only runs also
needed the listener and kind DNS PRs, and the agentgateway runs the egress
authority PR. Some microVM tests timed out under nested-virt load at
parallelism 4 and passed when rerun at parallelism 2.
AI use: I used Claude Code to write the code and tests and to run the tests
above. I reviewed every change and can explain it.