pal-e-docs

Phase 21: Progressive Delivery (Argo Rollouts)

phase-platform-21-progressive-delivery Phase

phase
Project

Phase 21: Progressive Delivery (Argo Rollouts)

Goal: Canary deployments gated by SLO burn rate — deploy fast, fail safely. The bridge between security hardening and advanced validation.
Owner: Dev agent
Repo: forgejo_admin/pal-e-platform (Rollouts controller) + forgejo_admin/pal-e-deployments (Rollout specs)
Depends on: Phase 16 (SLO Governance — canary promotion requires SLO metrics to evaluate against)
Tier: 2 — Hardening. Progressive delivery bridges "we hardened the platform" and "we can prove it under real traffic." Canary analysis uses SLO burn rate as the promotion gate.
DORA: DF + CFR — enables higher deployment frequency with lower failure rate. Automated canary analysis catches regressions that unit tests miss, without requiring manual validation.

Scope

  • Deploy Argo Rollouts controller via Helm in argo-rollouts namespace
  • Convert one service (pal-e-docs) from Deployment → Rollout with canary strategy:
  • Kustomize overlay in pal-e-deployments for Rollout resource
  • GitOps drift detection: alert when ArgoCD detects out-of-sync state persisting >5 minutes
  • Grafana rollout dashboard: canary vs stable metrics, promotion/rollback history
  • SOP: update sop-platform-tf-changes with rollout management procedures

Deliverables

  • TBD — filled after completion
  • plan-pal-e-platform — parent plan
  • phase-pal-e-platform-16-slo-error-budgets — SLO burn rate is the canary promotion gate
  • phase-platform-22-load-testing — load tests validate capacity for canary traffic splitting
  • convention-kustomize-overlay — Rollout specs follow existing overlay convention