Repository navigation
refactor(policy): stage UniFi validating guards - #5462
Conversation
Local validation at
This is the additive phase of #5459. The legacy policy is unchanged and remains enforced. After normal protected delivery I will bind the live replacement readiness to the published source before proposing its removal. The issue remains open until that removal and its runtime verification are complete. |
The first hosted run correctly rejected my combined policy file: this repository requires one Kubernetes resource per file. Corrected at The exact hosted naming-validator revision now passes locally. The complete policy suite still passes all 920 outcomes and all 99 fixture files satisfy the evaluation guard. Both CLI versions retain the characterized results; the six weakened-policy controls and three independent group/resource-pair controls still fail as intended. All 53 approved failure actions match source and rendered production policies. Both static configurations and all ten manifest layers validate, with the previously recorded offline warnings retained. This head also includes the independently validated protected-release change from current main. Fresh native CI is 40584911484; review and runtime acceptance remain pending. |
@coderabbitai full review |
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 24 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Bravo. 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". |
Readiness rechecked at Operator evaluation used the real Kyverno 1.19.2 CLI against the replacement policies alone. CREATE requests produced four allowed and nine denied cases; DELETE requests produced two allowed and five denied cases, with zero evaluation errors. These expected denials independently demonstrate the policy outcomes. The full 920-case suite, both supported CLI versions for the focused cases, six guard-removal controls, exact scope controls, rendered layers and naming checks also passed. The native code-quality rule has no readable per-head analysis surface, so its independent audit remains UNVERIFIED; the normal protected merge API must enforce it. No bypass is requested. This is the additive stage only: the original policy stays deployed until all three replacements are observed ready, followed by a separately reviewed removal. #5459 remains open through that final verification. |
Why
Kyverno is retiring the validation API used by the UniFi guard. The migration must preserve protection against changes that could delete managed network configuration.
What
Adds equivalent replacement guards and verifies that they preserve the existing admission outcomes. The current guard stays active until the replacements are confirmed ready; its removal follows in a separate protected change.
Part of #5459