delivery-release-gate

Plan a safe Kubernetes rollout by selecting a deployment strategy like canary, blue-green, or rolling updates based on blast radius, and ensuring rollback steps are defined and tested in staging before production deployment.

Sequence backward-compatible database migrations by applying schema changes before code deployment, ensuring old application versions tolerate new schemas, and verifying rollback paths in staging to prevent migration lock-in.

Handle feature flags during a release by ensuring they are disableable, validated in staging, and configured so any deployment can be reverted or feature toggled off without requiring a full code rollback.

Verify staging parity by validating that secrets and environment configuration match production, confirming immutable artifact tagging, and checking that the staging environment accurately reflects the target deployment environment.

Set up post-release monitoring by defining an owner-based verification window, establishing monitoring ownership, and creating a communication plan that includes compliance evidence for regulated or incident-driven releases.

Choose a canary deployment strategy when the blast radius of a release is high and gradual traffic shifting is needed, whereas blue-green offers instant rollback and rolling updates suit lower-risk progressive delivery.