Skip to content

Cutover Preconditions - oep-stg

Checklist to verify before initiating traffic cutover from AWS to DOKS for oep-stg.

Owned by: BD-7.5. Handed to: AWS to DO Backend Cutover: oep-stg Linear project. AWS deploy lane no longer functional post-UNI-53 (GH org SENTRY_AUTH_TOKEN deleted). Do not re-trigger legacy *-pipeline.yml workflows. Cutover proceeds DO-only.

Checklist

  • [ ] All pods healthy for 7+ days (no crashloops, no OOMKills)
  • [ ] Alerts quiet for 7+ days (no P1/P2 firing on DOKS side)
  • [ ] Parity smoke matrix green (bash scripts/smoke.sh oep-stg)
  • [ ] Data migration DM-6 complete (see aws-to-do-data-migration plan)
  • [ ] Secrets snapshot taken (Doppler export or equivalent)
  • [ ] DNS rollback plan staged (Cloudflare DNS values for AWS target documented)
  • [ ] Monitoring dashboards verified (Grafana, Prometheus, Loki)
  • [ ] PreSync migrate Job tested with real migration

Sign-off

Role Name Date
Tech Lead
On-call Engineer