gitops-patternslisted

# GitOps Patterns Best practices for operating infrastructure and applications through Git as the single source of truth. Covers ArgoCD, Flux, Argo Rollouts, environment promotion, secret management, and progressive delivery. ## GitOps Principles GitOps extends Infrastructure as Code by adding a reconciliation loop that continuously ensures the live system matches the declared state in Git. | Principle | Description | Implementation | |-----------|-------------|----------------| | Declarative | Entire system described declaratively | Kubernetes manifests, Helm charts, Kustomize overlays | | Versioned and immutable | Desired state stored in Git | Git commits as audit trail, tags for releases | | Pulled automatically | Software agents pull desired state | ArgoCD, Flux controllers watch Git repos | | Continuously reconciled | Agents correct drift automatically | Reconciliation loop detects and fixes divergence | | GitOps vs Traditional CI/CD | GitOps | Traditional CI/CD | |-----------------------------|--------|-------------------| | Deployment trigger | Git commit (pull-based) | Pipeline step (push-based) | | Source of truth | Git repository | Pipeline state / manual | | Drift handling | Auto-corrected | Undetected until next deploy | | Rollback method | `git revert` | Re-run pipeline with old version | | Audit trail | Git log | Pipeline logs (often ephemeral) | | Credential exposure | Cluster-only (no CI secrets) | CI system has deploy credentials | ## Repository Structu