test(ci): exercise restricted tenant admission#90
Conversation
Exact-head readiness evidence (
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 674e0befde
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Exact-head follow-up evidence (
|
|
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Why
The scaffold promises day-one compatibility with the platform's Pod Security
restrictedlevel, but its existing offline policy gate explicitly cannot exercise namespace-label Pod Security Admission. A tenant could therefore inherit a rollout-blocking security regression behind green template checks.What
Adds a pinned Kubernetes admission path that derives the Pod produced by the scaffolded Deployment, proves the valid Pod is accepted, and proves representative root, privilege-escalation, and capability mutations are denied. Structural mutation tests keep the job, versions, server admission, Pod conversion, and negative coverage fail-closed.
Fixes #89 · Part of #6