GitOps Rollouts Without Drama

Program narrative

We rehearse progressive delivery with canaries, sync waves, and secret handling that respects external reviewers. Labs emphasize reconciliation loops, diff discipline, and how to pause pipelines without hiding state from teammates.

Inclusions

• ApplicationSet patterns for many teams, few clusters
• Secrets strategies that avoid committing ciphertext by accident
• Hooks versus analysis templates tradeoffs
• Disaster recovery when Git is briefly unavailable
• Writing rollback criteria before rollout starts

Outcomes you can evidence

• Ship a change with two automated gates and one manual gate
• Document a failed sync and the fix without rerunning blindly
• Teach a partner how to read a live diff in under five minutes

Common questions

Flux instead?

Mentioned comparatively but labs stay Argo-first for this cohort.

Helm?

Support after class?

From our cohorts