Deploy · GitOps delivery
Argo CD
Argo CD reconciles Kubernetes clusters to the state declared in Git, with automated sync, pruning, self-heal, project-scoped RBAC and a UI/CLI for diffing and rollbacks.
On this page
What it does
Watches Git repositories (plain manifests, Kustomize, Helm) and applies changes to target clusters, reporting sync and health status.
Where it fits
Deploy stage in a pull-based model: CI never holds cluster credentials; Argo CD pulls from Git.
Quick start
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
argocd admin initial-password -n argocd
argocd app diff payments-apiCommon pitfalls
- Leaving the built-in
adminenabled after SSO is configured. - Projects without
sourceRepos/destinationslimits let any team deploy anywhere. - Fighting controllers (HPA, webhooks) instead of declaring
ignoreDifferences.
On this site
- Argo CD ApplicationSets for Multi-Environment Delivery: one ApplicationSet generating dev, stage and prod Applications from config files, manual sync on production, and deletion policy, run on kind.
- Platform Guardrails with Kyverno and GitOps: policies and exceptions as platform-project Applications beside the workload ApplicationSet, with
managedNamespaceMetadatalabels the policies select on.
Articles about Argo CD
Argo CD ApplicationSets for Multi-Environment Delivery
Replace hand-copied Argo CD Applications with an ApplicationSet driven by per-environment config files: the Git file generator, templatePatch for automated versus manual sync, AppProject boundaries and deletion policy.
Platform Engineering Foundations: Defining the Platform Contract
The operating model behind the CI templates, ApplicationSets, Kyverno guardrails and observability stack on this site: what a team hands over, what the platform returns, where the golden path ends and enforcement begins.
Platform Guardrails with Kyverno and GitOps
Kyverno as a platform guardrail system: baseline and production policy layers keyed on namespace labels, delivered by Argo CD from one repository, rolled out audit-first, with scoped expiring exceptions.
GitOps Deployment with Argo CD
Install Argo CD, model applications and projects, enable automated sync with pruning and self-heal, and lock the control plane down so Git really is the only way to change the cluster.