You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow explicitly selected sandbox workload UID/GID values across the full usable non-root Linux range instead of imposing an arbitrary system-user cutoff. Root and the invalid identity sentinel remain rejected, while the egress-exempt Kubernetes proxy UID retains its stricter infrastructure boundary.
This is a simpler alternative to #2737: it requires no new gateway configuration or min/max propagation.
Label test:e2e applied for b7ec28b. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.
Label test:e2e applied for b7ec28b. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.
Label test:e2e-kubernetes applied for b7ec28b. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute Kubernetes HA and credential-driver E2E after building the required gateway and supervisor images once. This is an optional proof-of-life suite; failures are visible in the workflow run but do not publish a required CI gate status.
Label test:e2e-kubernetes applied for b7ec28b. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute Kubernetes HA and credential-driver E2E after building the required gateway and supervisor images once. This is an optional proof-of-life suite; failures are visible in the workflow run but do not publish a required CI gate status.
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
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
Allow explicitly selected sandbox workload UID/GID values across the full usable non-root Linux range instead of imposing an arbitrary system-user cutoff. Root and the invalid identity sentinel remain rejected, while the egress-exempt Kubernetes proxy UID retains its stricter infrastructure boundary.
This is a simpler alternative to #2737: it requires no new gateway configuration or min/max propagation.
Related Issue
Fixes #2707
Changes
1through42949672940) and the Linux invalid-ID sentinel (4294967295)1000Testing
mise run pre-commitpassestest:e2eandtest:e2e-kubernetes)mise run testpassesmise run cipasses in a clean system-gateway filesystem viewChecklist