Plan a Platform Rollout
Use this for infrastructure changes. Policy activation has a separate Deploy Policy Changes procedure.
Prerequisites
Section titled “Prerequisites”Retain current version, rendered config, values, secrets, data backup, and schema-compatibility decision. Prepare readiness, authorization, revocation, and audit checks.
Procedure
Section titled “Procedure”- Verify provenance and render exact configuration.
- Review migrations, Secret keys, endpoints, NetworkPolicies, volumes, resources, and alerts.
- Confirm storage/event health.
- Apply migrations, then roll via supported runtime or Helm path.
- Stop on migration, readiness, audit, outbox, policy, revocation, or STS-exchange failure.
- Resume only after canary authorization and audit evidence.
Verify
Section titled “Verify”Record migration, rollout, /ready, queues/replay, metrics, and allow/deny canary request IDs.
Rollback or Recovery
Section titled “Rollback or Recovery”Use prior app/config only when schema-compatible; otherwise roll forward. Restore data only for declared disaster recovery, not ordinary rollback.
Next Step
Section titled “Next Step”Complete Hand Off to Platform Teams.