GitOps at Scale: Secrets, Rollouts, and Many Clusters
Keeping secrets out of Git, every deployment strategy with Argo Rollouts, ApplicationSets across clusters, Flux, and running GitOps in production.
Stage 1 gave you a working GitOps loop for one cluster. Real platforms add three hard problems: secrets (Git is the source of truth, but passwords can't live in it), safe releases (a merge shouldn't mean 100% of users get the new version instantly), and scale (dozens of services across several clusters and regions). This stage solves each one in the same repo.
+ ShopLite gains: secrets from AWS Secrets Manager, canary and blue-green releases with automated analysis, ApplicationSets generating apps for every cluster, and a production operations checklist
- 2.1
Secrets in GitOps: Sealed Secrets, SOPS, and External Secrets
ShopLite's Redis password and DB credentials reach the cluster without ever sitting in Git as plain text.
50 minFree locally; Secrets Manager ~$0.40/secret/month2 break-its - 2.2
Every Deployment Strategy, with Argo Rollouts
ShopLite web ships by canary with automated Prometheus analysis and auto-rollback, and the checkout service ships blue-green with a preview stage.
70 minFree2 break-its - 2.3
ApplicationSets and Multi-Cluster GitOps
One ApplicationSet generates every ShopLite service for every environment and cluster, so adding a service or a cluster is a single commit.
50 minFree — two kind clusters2 break-its - 2.4
Flux, Promotion Pipelines, and Running GitOps in Production
Know Flux well enough to work in a Flux shop, automate environment promotion, and harden Argo CD for production: SSO, RBAC, HA, notifications, metrics, and disaster recovery.
50 minFree1 break-its