The guestbook Application deploys apps/guestbook from Git with manual sync. A teammate ran kubectl scale during an incident and forgot to undo it.
About this scenario
The guestbook Application deploys apps/guestbook from Git with manual sync. A teammate ran kubectl scale during an incident and forgot to undo it.
Git says 2 replicas. Find the drift, fix it the GitOps way, and make sure it can't happen silently again.
Objectives
- See the Application OutOfSync
- Sync it back to 2 replicas
- Enable automated sync with selfHeal
- Scale it by hand again and watch Argo CD undo it
What you'll practice
- Argo CD compares every field Git sets with the live object. A manual change shows up as OutOfSync.
- Manual sync leaves drift alone until someone acts; selfHeal reverts it within seconds.
- In GitOps, the fix for drift is a commit, or a sync back to what Git already says.
How the playground works
The cluster runs entirely in your browser: a simulated API server, scheduler, kubelets and controllers, with virtual nodes in three zones. kubectl output follows the real formats, errors use the real messages, and the add-ons (CSI storage, Traefik, Envoy Gateway, cert-manager, Flux, Argo CD) behave like their real counterparts for the common paths. It's a simulation, so some behavior is simplified. Your progress is saved in this browser.