What is this?
Argo CD is a declarative GitOps continuous delivery tool for Kubernetes that keeps your cluster state synced with a Git repository.
Is this a CLI tool or does it run as a service in my cluster?
It's a server-side GitOps controller that runs inside your Kubernetes cluster, plus a CLI and web UI to interact with it.
How do I get it running?
You deploy Argo CD into your Kubernetes cluster and point it at a Git repo containing your application manifests; the documentation site walks through the full installation.
What do I need before installing it?
A running Kubernetes cluster is required, since Argo CD deploys as controllers and services on top of it, and it supports apps defined with plain YAML, Helm, Kustomize, or Jsonnet.
Does it work with any Kubernetes manifest format?
Argo CD natively supports multiple config management tools (plain manifests, Helm charts, Kustomize, ksonnet, Jsonnet), but your application definitions need to be declarative and version-controlled for it to manage them.
Who typically needs a tool like this?
Teams running production workloads on Kubernetes who want automated, auditable deployment and lifecycle management instead of manual kubectl applies.
What is the core GitOps idea behind Argo CD?
Application definitions, configurations, and environments are stored declaratively in Git, and Argo CD continuously reconciles the live cluster state to match that source of truth.
How does Argo CD compare to tools like Jenkins X or Spinnaker?
It focuses specifically on GitOps-style continuous delivery for Kubernetes rather than general CI pipelines; community articles compare it directly against Spinnaker, Jenkins X, and Tekton.
What are similar projects?
argo-workflows, kubesphere, Jenkins-Zero-To-Hero, jenkins, meshery, kubescape, charts, harness
Which topics is it in?
argo, continuous-delivery, continuous-deployment, gitops, cicd, pipeline, helm, cncf, infrastructure-as-code, ci-cd, kubernetes, hacktoberfest

