Lab trackArgo CD Labs

Argo CD hands-on labs

Twenty-two labs that take one real four-service application from kubectl apply to a production cluster run entirely from Git with Argo CD — sync, self-heal, prune, waves, promotion, sealed secrets and ApplicationSets on a live Kubernetes cluster.

  • 22 labs
  • 14.6 h
  • Intermediate
  • Free
Start with the first lab

Free with a free account — it runs in your browser, nothing to install.

  • A real environment in your browser
  • You run the commands yourself
  • Your result is checked automatically

Labs in this track

22 labsFree

Before GitOps

3 labs

Argo CD Fundamentals

5 labs
  1. Install Argo CD40 min
  2. Your First Application45 min
  3. Refresh, Diff, Sync40 min
  4. Synced Is Not Working40 min
  5. A Repository A Team Can Read35 min

Sync You Can Trust

5 labs
  1. Let It Sync Itself40 min
  2. Self-Heal35 min
  3. Prune, And What It Will Not Touch40 min
  4. Order Inside A Sync40 min
  5. Rolling Back For Real45 min

Real Delivery

5 labs

Scale And Operate

4 labs

About this track

A lab-only path that starts without GitOps, so every feature Argo CD has afterwards is an answer to something you have already lived through.

Show more

Every lab is a real Kubernetes cluster in your browser, and the same application runs through the whole track: a shop with a front end, two APIs and a message queue. First you deploy it by hand, drift it and put it back, then make a Git repository the truth. Then you install Argo CD, join the repository to the cluster with one Application and learn to read Synced and Healthy as two different facts. In the middle of the track you hand Argo CD its three permissions one at a time — apply, correct, delete — order a sync with hooks and waves, and recover a broken release the GitOps way. The last two sections are real delivery: a Helm chart and a Kustomize overlay as sources, two environments promoted by a commit, secrets you can commit, a project boundary, app-of-apps, ApplicationSets, and a capstone that bootstraps production from an empty cluster.

There are no video lectures and no reading-only lessons. Each lab states the task, checks what you actually did on the cluster, and shows a worked solution when you ask for one.

What you'll learn

  • Deploy a multi-service application by hand, drift it, and see exactly what GitOps replaces
  • Make a Git repository the source of truth and undo a bad change with a commit
  • Install Argo CD, reach its interface and retire the generated admin password
  • Write an Application, sync it, and trace a commit to the cluster by its sha
  • Tell Synced from Healthy, and lay out a repository a team can read
  • Turn on auto-sync, self-heal and prune, and know exactly how far each one reaches
  • Order a sync with hooks and sync waves, and roll back through the repository
  • Use a Helm chart and a Kustomize overlay as sources, and override values from the Application
  • Run two environments from one repository and promote a change with a commit
  • Commit secrets safely with Sealed Secrets, and fence an Application in with an AppProject
  • Deploy Applications with an Application, generate them with ApplicationSets, and ignore fields you do not own
  • Bootstrap production from an empty cluster without touching it by hand

Prerequisites

The Kubernetes hands-on labs, or the same ground from experience: comfortable with kubectl, Deployments, Services and namespaces, and with basic Git. The Helm labs help for the chart source lab but are not required.

Nothing to install. The cluster, the terminal, the Git server and an editor are in your browser.

Who it's for

DevOps and platform engineers moving a team from kubectl and CI scripts to GitOps, developers who ship to Kubernetes, and anyone preparing to run Argo CD in production.

FAQ

Do I need the Kubernetes labs first? Not formally, but every lab assumes kubectl. If Deployments and Services are new to you, start there; they are free.

How many times can I launch a lab? Ten launches per lab, one at a time.

Is it the same application all the way through? Yes. The shop you apply by hand in the first lab is the one you bootstrap from Git in the last.

Do I have to go in order? The labs build on each other, so in order is best, but each one prepares its own starting point and stands on its own.