Argo CD — Declarative GitOps Continuous Delivery for Kubernetes
Argo CD is a declarative GitOps CD tool for Kubernetes. Sync applications from Git repositories automatically, with visual diff, rollback, and multi-cluster support.
Instalación lista para agent
Este activo puede instalarse después de elegir el runtime, revisar el plan y ejecutar el comando correspondiente.
npx -y tokrepo@latest install ca164613-353d-11f1-9bc6-00163e2b0d79 --target codexEjecutar después de confirmar el plan con dry-run.
What it is
Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. It watches Git repositories containing your application manifests and automatically syncs them to your Kubernetes clusters. When someone pushes a change to the Git repo, Argo CD detects the diff, shows you what will change, and applies it. It supports Helm charts, Kustomize, plain YAML, and Jsonnet.
Argo CD targets platform teams and DevOps engineers who want Git as the single source of truth for their Kubernetes deployments. Instead of running kubectl apply manually or building custom CI/CD pipelines, Argo CD handles the deployment lifecycle declaratively.
Why it saves time or tokens
Manual Kubernetes deployments require running kubectl commands, tracking what version is deployed where, and hoping nobody made undocumented changes. Argo CD eliminates drift by continuously reconciling cluster state with Git. Rollback is instant: revert the Git commit and Argo CD redeploys the previous version. For AI-assisted infrastructure management, Argo CD reduces deployment to a Git push, which is simpler than generating kubectl commands.
How to use
- Install Argo CD in your cluster:
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml - Create an Application resource pointing at your Git repo and target cluster
- Argo CD syncs your manifests and shows deployment status in the web UI
Example
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: web-app
namespace: argocd
spec:
project: default
source:
repoURL: https://github.com/myorg/k8s-manifests.git
targetRevision: main
path: apps/web-app
destination:
server: https://kubernetes.default.svc
namespace: production
syncPolicy:
automated:
prune: true
selfHeal: true
| Feature | Description |
|---|---|
| Auto-sync | Deploy on Git push |
| Visual diff | See changes before applying |
| Rollback | One-click revert to any version |
| Multi-cluster | Manage multiple clusters |
| SSO | OIDC, LDAP, SAML authentication |
Related on TokRepo
- AI tools for devops — DevOps and Kubernetes tooling on TokRepo
- AI tools for automation — deployment automation and CI/CD tools
Common pitfalls
- Enabling auto-sync with prune: true deletes resources removed from Git; test this in staging before production
- Argo CD manages the deployment, not the build; you still need a CI system (GitHub Actions, Jenkins) to build images
- Secrets in Git repos must be encrypted (Sealed Secrets, SOPS, or External Secrets Operator); never commit plaintext secrets
Preguntas frecuentes
Both are CNCF GitOps tools for Kubernetes. Argo CD provides a rich web UI with visual diffs and a centralized multi-cluster management model. Flux uses a decentralized per-cluster approach with no built-in UI. Choose Argo CD for teams that value visual management; choose Flux for lightweight, per-cluster GitOps.
Yes. Argo CD natively renders Helm charts by running helm template during sync. You specify the chart repository, version, and values in the Application spec. Argo CD tracks the rendered manifests in Git, so you get the benefits of both Helm packaging and GitOps deployment.
Argo CD does not manage secrets directly. Use Sealed Secrets, SOPS, External Secrets Operator, or Vault to handle secret encryption and injection. Argo CD syncs the encrypted secret resources from Git, and the in-cluster operator decrypts them. Never store plaintext secrets in your Git repository.
Yes. Argo CD can deploy applications to any Kubernetes cluster it has credentials for. You register external clusters and target them in Application specs. A single Argo CD instance can manage dozens of clusters from one dashboard.
Self-heal automatically reverts manual changes made directly to the cluster. If someone runs kubectl edit to modify a resource that Argo CD manages, self-heal detects the drift and restores the resource to match the Git-defined state. This enforces Git as the single source of truth.
Referencias (3)
- Argo CD GitHub— Argo CD is a declarative GitOps CD tool for Kubernetes
- Argo CD Docs— Argo CD is a CNCF graduated project
- CNCF GitOps— GitOps principles for Kubernetes deployment
Relacionados en TokRepo
Discusión
Activos relacionados
Argo Rollouts — Progressive Delivery for Kubernetes
A Kubernetes controller that provides advanced deployment strategies like canary releases, blue-green deployments, and automated rollback with traffic management integration.
Kargo — GitOps Promotion and Application Lifecycle Orchestration
Orchestrate progressive promotion of changes across environments in a GitOps workflow. Kargo adds a structured promotion layer on top of Argo CD, handling verification gates and multi-stage rollouts.
Jenkins X — Cloud Native CI/CD for Kubernetes
Jenkins X provides automated CI/CD pipelines with GitOps promotion, preview environments on pull requests, and Tekton-based builds natively on Kubernetes.
Tekton Pipelines — Cloud-Native CI/CD Primitives for Kubernetes
Tekton Pipelines is a powerful, flexible, open-source framework for creating CI/CD systems. It runs pipelines as native Kubernetes resources using Tasks, Pipelines and TaskRuns.