Container Registry and Software Supply Chain Platform · View 31 of 33 · 6 · Assurance
Decisions
- Revocation is an identity operation: the SPIRE entry is removed, the Fulcio identity is banned, the robot account is disabled
- The signer allowlist is rebuilt into a new policy bundle, so revocation propagates by the same path as any policy change
- Artifacts are not deleted; they simply stop satisfying policy
Targets
- Revocation to full enforcement-point propagation p95 ≤ 5 minutes, p100 ≤ 15 minutes
- Every affected artifact is enumerable by signer identity, which is why signer identity is a column and not a blob
- The rebuild plan names what must be rebuilt under a new identity
The bounded blast radius
- Running pods continue to run; revocation changes the next admission, not the current state of the cluster
- Draining them is the same phase-3 mechanism as verdict-change eviction
- Air-gapped sites propagate on the transport interval, not the 5-minute target — and deny on revocation-list age