GitOps with Argo CD and Argo Rollouts
Learn GitOps with Argo CD: sync apps from Git, promote across environments, scale with ApplicationSets, and ship safely with Rollouts canaries.
What You'll Learn
Understanding Why GitOps Exists
acme-shop's platform team has cart-service running on Kubernetes, deployed by hand with kubectl apply.
Applying the Four GitOps Principles
The OpenGitOps project defines GitOps through four principles. Every Argo CD feature maps to one of them.
Understanding Argo CD Architecture and Installation
Argo CD runs as a few pods inside your cluster. Knowing the three main parts tells you where to look when something breaks.
Creating Your First Application
An Application is a Kubernetes resource that says: take manifests from this Git path and keep this namespace in sync with them.
Rendering Manifests With Kustomize and Helm
Argo CD renders Kustomize and Helm for you. You commit the source, and it builds the final manifests.
Managing Many Applications at Scale
One Application per service works for five services. For fifty, you need patterns that create Applications for you.
Skills You'll Master
Curriculum Index12 topics
Understanding Why GitOps Exists
acme-shop's platform team has cart-service running on Kubernetes, deployed by hand with kubectl apply.
Applying the Four GitOps Principles
The OpenGitOps project defines GitOps through four principles. Every Argo CD feature maps to one of them.
Understanding Argo CD Architecture and Installation
Argo CD runs as a few pods inside your cluster.
Creating Your First Application
An Application is a Kubernetes resource that says: take manifests from this Git path and keep this namespace in sync...
Rendering Manifests With Kustomize and Helm
Argo CD renders Kustomize and Helm for you. You commit the source, and it builds the final manifests.
Managing Many Applications at Scale
One Application per service works for five services. For fifty, you need patterns that create Applications for you.
Handling Drift and Debugging Sync Problems
Drift is the cluster differing from Git. Some drift is a real problem and some is normal.
Choosing Between Argo CD and Flux
Both are mature GitOps tools that implement the same principles. This module teaches Argo CD.
Shipping Safely With Argo Rollouts
A Kubernetes Deployment replaces pods gradually, but it cannot pause at 20 percent and check whether users are hurt.
Organising the GitOps Repository and Promotions
Repository layout decides how easy promotions and rollbacks are.
Building the Hands-On GitOps Lab
You will deploy cart-service from a Git repository you own, auto-sync staging, promote production by tag, and ship and...
Quick Reference and Common Mistakes
Quick reference Common mistakes Production that syncs itself while the comments say it does not is a quiet disaster.
Career Impact
Roles that use the skills in this module.
DevOps Engineer
Site Reliability Engineer
Platform Engineer
Next Modules
Related Guides
Practice on the Coding Sheet
Not a software engineer sheet. Every problem comes from real DevOps, SRE, Platform and Cloud interviews, from your first script to a system you build yourself.
Open the Coding SheetFrequently Asked Questions
GitOps means Git holds the desired state of your system, and an agent inside the cluster keeps the cluster matching it. You change the system by changing Git, not by running commands against the cluster. Rollback becomes a git revert.
No. CI builds, tests, and publishes an image. Argo CD takes over after that and deploys what Git says. Most teams use both, with CI updating an image tag in the GitOps repository.
Argo CD syncs manifests from Git into a cluster. Argo Rollouts replaces the Deployment object with a Rollout that can shift traffic gradually and roll back. They are separate tools that work well together.
Many teams sync staging automatically and keep production manual, tracking a Git tag or a protected release branch. That puts a human decision, or a reviewed pull request, between a merge and production.