Repository navigation
fix(kyverno): publish reports watch-planning correction - #5465
Conversation
@coderabbitai 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 44 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 |
cr:no-gate@72b7fb5 — CodeRabbit's authenticated repository quota receipt says the next included review is available 30 minutes after 22:28:41 UTC, or 22:59:41 UTC with margin. Its command reply confirms the review did not run. Complete current-head reads show no delivered review or finding, and the no-gate guard admits this record. Advancing once to Codex under this head's owned review lock. |
@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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 72b7fb5da4
ℹ️ 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".
@coderabbitai review |
|
cr:no-gate@00809fb — CodeRabbit's authenticated response to this head's request states that the review did not run because it is rate limited. Fresh complete discussion/review/thread reads show no CodeRabbit review or finding at this head, and the live no-gate guard admits this record. The earlier Codex P2 is fixed and its thread resolved. Current Linux image verification and CI are green. Advancing once to Codex under the owned request lock. |
@codex review |
|
Codex Review: Didn't find any major issues. Keep it up! 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 at User evaluation exercised the actual controller's Warmup/List/Watch behavior, including healthy-plus-unavailable resources and removal of obsolete watches. The affected resource, aggregation and admission race suites, pinned Go/linter checks, static Linux build and exact release-to-patched-tree replay pass. The factory builds the actual controller into the pinned original runtime image and runs its startup help probe. Private native discovery/RBAC replay was a preflight only; it is not production adoption. The full upstream generator run remains incomplete because its CLI generator requires an unavailable local cluster; no upstream contribution or generator-completion claim is being made. The signed branch is clean, GitHub reports CLEAN, every readable required check/workflow passes, and the live-health gate exits zero during the active deployment queue. Native code quality remains independently UNVERIFIED and is left to protected enforcement. Promoting for the normal queue. Signed publication, separate image adoption, refreshed native coverage and a quiet error window remain acceptance gates on #4929. |
Why
Background security reporting attempts unrelated reads and misses some resources matched by deployed policies. This creates persistent errors and leaves reporting coverage uncertain.
What
Builds and signs a correction for the deployed release that follows each policy's background scope while preserving errors for incomplete observations. Deployment and live reporting recovery remain separate acceptance steps.
Part of #4929