~/ nmadiraju.com Amazon EKS · Argo CD and GitOps
arrow_back Back to nmadiraju
Visual Walkthrough · Delivery and operations

How Argo CD and GitOps Work on Amazon EKS

Follow web's manifests from Git into an EKS cluster through Argo CD, then check yourself with 8 questions.

1Visual Walkthrough

A self-managed Argo CD in an EKS cluster syncing the web app's manifests from a Git repository Left, a developer, a CI pipeline and an on-call engineer. Next, the Git repo acme/platform-config with apps/web manifests. Right, EKS cluster shop-prod: namespace argocd with the Application web, repo-server and application-controller, and namespace web with the live Deployment, Pods, Service and web-canary. The walkthrough replaces a push-based CI deploy with GitOps, syncs a new image tag, recovers a Degraded release with git revert, and shows selfHeal undoing a hand edit and prune deleting a removed object. Priya · developer reviews and merges PRs CI · GitHub Actions builds the web image Sam · on-call has kubectl access GIT · acme/platform-config branch main protected: changes only by PR DELETED apps/web/deployment.yaml replicas: 3 the desired state of web DELETED apps/web/service.yaml port 80 → 8080 DELETED apps/web/web-canary.yaml Deployment web-canary an old experiment DELETED EKS CLUSTER shop-prod · us-east-1 NAMESPACE argocd · SELF-MANAGED Application web repo acme/platform-config path apps/web · rev main → in-cluster · ns web repo-server clones Git, renders manifests plain YAML, Kustomize or Helm application-controller compares desired with live applies the difference on sync using its own credentials NAMESPACE web · LIVE STATE Deployment web Pods Service web ClusterIP · port 80 → 8080 Deployment web-canary 1 replica · web:1.3-rc from web-canary.yaml PRUNED

    2Quiz to check understanding

    Check yourself