GitOps & Progressive Delivery

GitOps treats Git as the single source of truth for infrastructure and application state. Controllers continuously reconcile the desired state (in Git) with the actual state (in the cluster), eliminating manual kubectl apply in production.

When to Activate

• Setting up ArgoCD or Flux for Kubernetes deployments
• Designing GitOps repository structure (mono-repo vs. config-repo)
• Configuring multi-cluster GitOps with ApplicationSets
• Managing secrets in a GitOps workflow (Sealed Secrets, External Secrets Operator)
• Migrating from imperative kubectl workflows to declarative GitOps
• Configuring drift detection and automated remediation

For canary/blue-green deployments and automated rollback with Argo Rollouts — see skill progressive-delivery.

GitOps Core Principles

Four principles from the OpenGitOps standard: