Repository navigation
Open
Description
Parent: Deliver Galactic Worker with Local and Fabric delivery for tenant services
Deliverable
One Envoy proxy serves local and remote backends through VRF-bound upstream sockets, with the galactic-vrf sidecar consuming Worker attachments. It satisfies the ALB part of the "Deliver service consumers" phase exit.
References:
- Sidecar:
cmd/galactic-vrfandinternal/ingresssidecar(store.go,ebpfdatapath.go,gatewayreply.gowithensureGatewayReplyRedirect). - Host-return writer to move under Worker:
internal/installer/sidecarreturn.go. - The image is
containers/galactic-vrf/Dockerfile. Noconfig/galactic-vrfmanifest exists, so this Task ships one.
PR #1384 changes redirect-route cleanup in internal/ingresssidecar. If it has merged to main before this PR, incorporate it into the branch and record that. Otherwise this PR carries the same rule: remove a redirect route only through its own VRF.
Work items
- Have the sidecar request the host attachment and own the pod-side VRF, gateway address and tenant routes. Share one pod-to-host routed pair per attached VPC. Use the physical locator and current host attachment to choose a local backend route or a remote encapsulating route.
- Install the gateway return /128 in the canonical host VRF ahead of default NAT, and keep remote reachability.
- Fence link and advertisement transfer by proxy pod UID. Serialize replacement unless overlapping ownership is implemented and tested.
- Add the
config/galactic-vrfmanifest component, covered bytask test:manifests. - Expose the sidecar's Worker capability state and failure reasons through existing diagnostics and metrics.
Dependencies
Blocked by #1434, #1435 and #1436. Runs in parallel with #1437, #1438 and #1440.
Acceptance
Run in the #1432 topology:
- HTTPS requests complete through one proxy into two VPCs with overlapping backend addresses, on both fresh and reused connections. Captures and socket reads show that each upstream socket receives the correct reply with the right source.
- Moving an endpoint off-node, deleting the last TAP and replacing the proxy each leave the successor and other tenants working, and cleanup removes only the old owner's state.
task test:manifestsrenders the new component.- The delivering PR targets
integration/galactic-worker, carries this evidence and saysFixes datum-cloud/galactic#1439. GitHub does not auto-close from a non-default base, so close this issue explicitly when the PR merges and record the PR and merged SHA.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Activity