pilot-rollback-decision

To determine the safest Kubernetes rollback target, evaluate candidate prior revisions using receipt verification and blast-radius impact analysis. This produces a structured safety verdict—PASS, WATCH, BLOCK, or INCONCLUSIVE—for each candidate, identifying the most recent revision that passed verification.

A rollback safety verdict is a structured assessment that determines if a prior Kubernetes revision is safe to restore. It works by verifying revision-pinned receipts at each candidate commit and analyzing ConfigHub history to produce auditable PASS or BLOCK guidance for GitOps operations.

Evaluating blast-radius impact before a Kubernetes rollback involves previewing the potential effect of reverting to a candidate revision. By analyzing ConfigHub history and impact data alongside per-candidate receipts, you receive evidence-backed guidance on whether a target is safe or should be blocked.

Yes, you can audit the rollback decision chain by chaining per-candidate evaluation receipts into a final chosen-target receipt. Using input attestation preserves the full safety verdict rationale, ensuring the evidence behind a Kubernetes rollback target is completely traceable for post-incident reviews.

Yes, generating rollback safety verdicts requires ConfigHub connected-mode capabilities for history and impact analysis. These features enable the ChangeSet timeline review and blast-radius preview necessary to evaluate candidate revisions and produce a verified rollback target receipt.

You should avoid automated rollback target decisions when verification results are INCONCLUSIVE or BLOCK. If candidate revisions fail receipt verification or the blast-radius impact is unacceptable, the system prevents a rollback, requiring manual investigation before reverting the broken Kubernetes release.