← Back to snippets

ArgoCD GitOps Essentials: Quick Reference

February 1, 2026Salih Kayiplar

argocd
gitops
kubernetes
deployment

CIOps vs GitOps

CIOps (Push)GitOps (Pull)
HowCI pipeline pushes to clusterArgoCD watches git, syncs to cluster
Use forDev/test environmentsStaging/production

Core Concepts

ConceptWhat it means
ApplicationCRD grouping K8s resources from a manifest
Target stateWhat's in Git
Live stateWhat's in the cluster
SyncMaking live = target
RefreshComparing Git vs live
HealthIs the app actually running and serving?

Architecture

  • API Server: gRPC/REST for Web UI, CLI, CI/CD. Handles auth + RBAC.
  • Repo Server: Caches git repos, generates manifests from Helm/Kustomize/YAML.
  • App Controller: Watches running apps, detects OutOfSync, runs lifecycle hooks.

Supported config management

Kustomize, Helm, Jsonnet, plain YAML

Lifecycle hooks order

PreSyncSyncPostSyncSyncFail

Use for blue/green and canary with Argo Rollouts.

Gotcha

  • ArgoCD does not handle traffic shifting or canary analysis — pair it with Argo Rollouts for that
  • Healthy and Synced are independent — an app can be synced but unhealthy (e.g. CrashLoopBackOff)
  • Refresh interval is 3 minutes by default. For faster detection, configure webhooks (GitHub/GitLab/BitBucket)

Ready to scale your cloud infrastructure?

Let's discuss how CloudCops can help you build secure, scalable, and modern DevOps workflows. Schedule a free discovery call today.