Skip to content

Enable native Pods to use a VPC as their primary network - #472

Merged
scotwells merged 4 commits into
mainfrom
feat/native-pod-vpc-attachment
Oct 12, 2026
Merged

scotwells merged 4 commits into
mainfrom
feat/native-pod-vpc-attachment

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Why

Internal DNS needs one Pod on each compute and Connect gateway node, with Galactic as its primary VPC network. The same capability can support telemetry endpoints in consumer VPCs without introducing a DNS-specific deployment path.

What

  • Add opt-in, cell-local attachment for native Pods and DaemonSets. Compute holds each Pod behind a scheduling gate until its VPC interface is allocated and prepared, then starts it with Galactic as eth0.
  • Add a cell deployment overlay and focused controller/admission tests.
  • Add a product enhancement covering the user experience, acceptance criteria, and rollout dependencies.

Validation

  • go test ./internal/controller ./internal/webhook ./cmd -run 'TestPodNetwork' -count=1
  • kustomize build config/overlays/cell-pod-network
  • git diff --check github/main...HEAD

Before rollout

Establish a stable reference to Cloud's prepared NAD and verify late Multus annotation handling and detach/address release ordering in a cell. This PR is draft while those integration checks remain.

@scotwells
scotwells marked this pull request as ready for review October 12, 2026 16:33
@scotwells
scotwells requested a review from a team as a code owner October 12, 2026 16:33
@scotwells
scotwells marked this pull request as draft October 12, 2026 17:05
@scotwells
scotwells marked this pull request as ready for review October 12, 2026 17:06
@scotwells
scotwells merged commit af9d7d3 into main Oct 12, 2026
11 checks passed
@scotwells
scotwells deleted the feat/native-pod-vpc-attachment branch October 12, 2026 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants