Repository navigation
Conversation
Install and bind only the vendor port-forward rule by stable ID, preserving the other controller output and both switch states. Generate the one missing Rules schema property from the hash-verified pinned chart without changing existing catalog constraints. Part of #4968.
Validation at
This remains a draft: current-head hosted checks and review must complete, and live rule loading plus a controlled detector event and observed alert delivery remain named acceptance gates. Rendering and object presence do not establish delivery or full runtime coverage. |
Refreshed head The bounded runtime-rule render regression, generated-schema checks, authorization race suite, and local/production KSail validation pass. The changed Kubescape chart was rendered independently; broader validation retains its reported OCI credential-helper and offline namespace-label limitations. This remains draft pending current-head CI and review. The controlled detection and alert-destination acceptance for #4968 and #4264 still need deployment evidence. |
@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. What shall we delve into next? 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 for Operator evaluation follows the product's manifest-evaluation contract: actual Helm install and upgrade renders exercise both switch states, verify the exact R2001 definition and binding, and preserve unrelated rendered resources. The generated-schema and rejection controls, authorization race suite, and local/production KSail validation pass. Broader validation retains its reported OCI and offline namespace-label limitations; the changed chart was independently rendered. This establishes the intended declarative installation. Live rule loading, controlled detection, and alert-destination acceptance remain post-deployment work under #4968 and #4264. Those runtime gates are unverified and the parent work remains open. The fresh general live-health check exits zero. Native GitHub reports CLEAN; the completeness helper's unreadable code-quality analysis state remains UNVERIFIED under the consumer's ordinary CLEAN rule. |
Blocker: #5805 | upstream | last-verified 2026-11-03: Production public-contract timeout incident remains open. Mitigation PR #5807 is still OPEN and queued at reviewed head fc4b22c. Preserve this PR at 2dbc343 outside the queue. Resume only after #5807 merges and its native deployment receipt proves the public contract passed; re-read this PR's complete current-head gates and ownership before enqueueing. This repairs the record's date syntax without changing its resume conditions. |
Why
Runtime monitoring needs a small, verifiable detection baseline before broader rules can be enabled safely.
What
Enables the initial port-forward detection with stable matching and validation that follows the vendor's supported format.
Deferred: #4968 — broader runtime detection coverage.
Deferred: #4264 — end-to-end runtime alert delivery.
Part of #4968