docs: Add implementation plan for VPC ingress sidecar - #310
Open
privateip wants to merge 1 commit into
Open
Conversation
8 tasks
8 tasks
Contributor
Author
|
Same failing CI that is tied to #302 and will require a rebase once it is merged |
Adds a written implementation plan for datum-cloud/enhancements#855, mapping the sidecar's role in the accepted HTTP Ingress for VPC Networks design (enhancements#851) onto this repo's existing internal/plumbing/vrf and internal/plumbing/srv6 primitives, and resolving seven open engineering decisions surfaced while planning: a time-based teardown grace period (flagged for longer-term follow-up), inventory-before-reconcile startup safety, a recommended container name for #856's deployment patch, punting backend health-checking to a future issue, two required pre-merge kernel verification steps (seg6 encap route from Envoy's netns, and eBPF decap compatibility), and a noted (no-action) dependency on #856/#857 for cross-namespace HTTPProxy reference resolution. Related to datum-cloud/enhancements#855 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
privateip
force-pushed
the
docs/855-ingress-sidecar-plan
branch
from
August 8, 2026 18:03
5253d38 to
07b2066
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.
Summary
datum-cloud/enhancements#855 asks for a sidecar that runs alongside Envoy Gateway pods, per the design accepted in datum-cloud/enhancements#851. This adds a written implementation plan mapping that sidecar's job onto this repo's existing
internal/plumbing/vrf/internal/plumbing/srv6primitives before any code is written.It also resolves seven open engineering decisions surfaced while planning:
galactic-vrf, with latitude for the implementer to rename.seg6encap route run from an Envoy Gateway pod's netns specifically, and end-to-end decap compatibility with the existing eBPF uSID datapath.HTTPProxyreference: noted as a dependency on #856/#857 with no action needed from this sidecar.Test plan
Related to datum-cloud/enhancements#855