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
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 16 min
The stable manifests move. The behaviour shown here - the annotation limit, self-heal, prune scope - is not version specific.
- Argo CDstable manifests, 2026-08
- Source repoargoproj/argocd-example-apps
| 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 |
This guide includes
Use this when a workload should be deployed from Git and then kept that way. This matters because Argo CD's Application is an ordinary Kubernetes object of about twenty lines, and neither the CLI nor the UI is the source of truth.
- declaring an Application that points at a Git repository and path
- recognising that an empty SYNC and HEALTH immediately after creation is not an error
- reading back the exact Git revision Argo CD deployed, not merely Synced and Healthy
- confirming the Deployment, Service and Pods it created in the target namespace
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