docs: Add implementation plan for VPC ingress EndpointSlice work - #309
Open
privateip wants to merge 1 commit into
Open
docs: Add implementation plan for VPC ingress EndpointSlice work#309privateip wants to merge 1 commit into
privateip wants to merge 1 commit into
Conversation
8 tasks
8 tasks
Contributor
Author
|
The failing CI check is due to #302 not being merged yet. Once it is merged, I will rebase this PR to clean up the CI failures. |
datum-cloud/enhancements#854 asks galactic-cni to publish per-pod SRv6 SID and tenant-identifier metadata so the shared Envoy Gateway ingress fleet can reach VPC-hosted backends, per the design accepted in datum-cloud/enhancements#851. This adds a written implementation plan before any code changes. It reconciles #854's original wording with the CNI's current chained-plugin architecture (the work lands in galactic-bgp, not the master plugin, since that's the only plugin in the chain with the pod address, SRv6 locator/nodeID, and allocated VRFID all in scope at once), lays out phased work items with file/line anchors into the existing codebase, and resolves four engineering questions the design left open: IPv6-only scope for this issue, a new discovery label for the not-yet-built extension server to key off, confirmation that galactic-bgp shares galactic-cni's ServiceAccount, and rollback semantics on partial ADD failure. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
privateip
force-pushed
the
docs/854-vpc-http-ingress-plan
branch
from
August 8, 2026 18:03
bb92f49 to
7cb3ab6
Compare
ecv
approved these changes
Aug 9, 2026
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
2 participants
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.
Summary
datum-cloud/enhancements#854 asks galactic-cni to publish per-pod routing metadata so the shared Envoy Gateway ingress fleet can reach VPC-hosted backends, per the design accepted in datum-cloud/enhancements#851. This adds a written implementation plan mapping that work onto the CNI's current plugin-chain architecture before any code is written. It also resolves four engineering questions the design left open: address-family scope, a new discovery label for a not-yet-built downstream component, service-account ownership, and rollback behavior on partial failure.
Test plan
Related to datum-cloud/enhancements#854