Skip to main content
Before an upgrade, run the package preflight, take a portable PostgreSQL dump, verify Cloud SQL PITR and object versioning, render and archive manifests, and review all permission, network, Secret, node placement, and image changes. Use Helm --atomic --wait. If readiness fails without a schema change, Helm returns to the prior revision. Migrations are forward-only and idempotent. A rollback across a schema change restores the pre-upgrade dump into a new database and deploys the previous image digest; never restore over the failed database. Quarterly restore drills verify migration ledger, record counts, audit export, receipt reads, recovery point, and recovery time. The support-bundle script collects bounded workload state, warning events, Helm history, and logs. It does not query Kubernetes Secrets, Helm values, source artifacts, diffs, evidence objects, or database rows. Operators must inspect it for unexpected customer data before sharing.
Last modified on July 28, 2026