Skip to content

Make the VRF sidecar's NET_ADMIN effective - #414

Merged
scotwells merged 1 commit into
proto/network-servicefrom
fix/vrf-sidecar-capability
Aug 27, 2026
Merged

Make the VRF sidecar's NET_ADMIN effective#414
scotwells merged 1 commit into
proto/network-servicefrom
fix/vrf-sidecar-capability

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

The VRF sidecar declares NET_ADMIN and cannot use it. Kubernetes does not set ambient capabilities, so an added capability only enters the effective set for uid 0, and the image is distroless:nonroot.

Creating the VRF device fails with EPERM. The container starts and passes its checks first, so this reads as a healthy sidecar.

Runs it as uid 0 holding NET_ADMIN alone, matching the staging channel so dev and e2e do not drift from what the edge runs.

Paired with datum-cloud/infra#4279.

Related: #411

Kubernetes does not set ambient capabilities, so an added capability only
enters the effective set for uid 0. The sidecar image is
distroless:nonroot, so NET_ADMIN was declared and inert, and creating the
VRF device failed with EPERM.

Match the staging channel, which carries the same fix, so dev and e2e do
not diverge from what the edge runs.

Key changes:
- Run the sidecar as uid 0 in the dev and e2e downstream configs
@scotwells
scotwells merged commit c20279a into proto/network-service Aug 27, 2026
10 checks passed
@scotwells
scotwells deleted the fix/vrf-sidecar-capability branch August 27, 2026 22:31
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.

1 participant