Hands-on Lab·Kubernetes and Cloud Native Associate
The Argo CD Application Resource
Point Argo CD at a Git path with twenty lines of YAML and it deploys, then keeps deploying. The Application object records the exact commit it reconciled, which is the difference between GitOps and a pipeline that ran once.
Delivery and GitOps Guide 43 of 46 Beginner
- Kubernetes1.36.4
- Argo CDstable manifests, 2026-08
- Source repoargoproj/argocd-example-apps
- TimeAbout 16 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
- Argo CD installed, all three CRDs present. The install guide covers the trap.
- No Argo CLI needed. Everything here is kubectl against a custom resource.
-
Declare it
-
Empty status is not an error
-
It records the commit, not just the outcome