Hands-on Lab·Kubernetes and Cloud Native Associate
GitOps Self-Heal and Prune
Scale a managed Deployment by hand and the change is gone before the next command runs. Then create a ConfigMap in the same namespace and watch prune leave it completely alone.
Delivery and GitOps Guide 44 of 46 Intermediate
- Kubernetes1.36.4
- Argo CDstable manifests, 2026-08
- Source repoargoproj/argocd-example-apps
- TimeAbout 15 min
- Reviewed22 August 2026
Written against the versions above. The stable manifests move. The behaviour shown here - the annotation limit, self-heal, prune scope - is not version specific.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- The guestbook Application from the previous guide, with
selfHeal: trueandprune: true.
-
Try to scale it
-
Patch it, same result
-
Prune only touches what it manages