e2e: reach an in-cluster destination over each address family - #1104
Open
Yuan Gao (ygao-g) wants to merge 1 commit into
Open
e2e: reach an in-cluster destination over each address family#1104Yuan Gao (ygao-g) wants to merge 1 commit into
Yuan Gao (ygao-g) wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
The egress suite fetches example.com, so which address families a test exercises is decided by whatever resolver the cluster inherited. When the name has no AAAA the actor never attempts IPv6 and a broken IPv6 path passes; when it does, the same test fails. Neither outcome says anything about the system. Adds an in-cluster destination fronted by three Services over one backend, so the families are a property of the test, and asserts the family the request actually arrived over rather than trusting a 200. The dual-homed case is the one no single-family cluster can construct: an actor with an IPv6 address prefers the AAAA, so that destination is unreachable the moment IPv6 egress breaks, even with a working A record alongside it.
Yuan Gao (ygao-g)
force-pushed
the
e2e-egress-family
branch
from
August 20, 2026 21:56
1ad89ea to
7d78195
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
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.
The egress suite fetches example.com, so which address families a test exercises is decided by
whatever resolver the cluster inherited. When the name has no AAAA the actor never attempts IPv6 and
a broken IPv6 path passes; when it does, the same test fails. Neither outcome says anything about
the system, and neither single-family lane can notice.
This adds an in-cluster destination fronted by Services pinned to each family, so which families are
in play is a property of the test, and asserts the family each request actually arrived over rather
than trusting a 200. The dual-homed case is the one no single-family cluster can construct: an actor
that has an IPv6 address prefers the AAAA, so that destination becomes unreachable the moment IPv6
egress breaks, even with a working A record right beside it and every IPv4-only destination still
working. Measured on a dual-stack kind cluster it passes on main and fails with #979 and #1057
applied, which is #1089. On a single-family cluster the cases it cannot build are skipped. Part of
#246.
🤖 Generated with Claude Code