GitOps with Argo CD · Module 02

Delivering Apps with Argo CD

Render Helm, Kustomize and plain YAML sources, choose sync policies (automated, prune, self-heal), order releases with sync waves and hooks, and promote versions between environments with pull requests and Git reverts.

Practice interactively →

What you will learn

• Deploy Kustomize overlays and Helm charts, including values from a separate repo
• Choose sync policies and sync options, and explain the risks of prune and self-heal
• Order resources with sync waves and run migrations and smoke tests as hooks
• Promote a version through environments with pull requests and roll back safely

Lessons

1. Helm, Kustomize and plain YAML sources

   The repo server detects the source type and renders it: a folder of YAML, a Kustomize overlay, or a Helm chart with values files and parameters.

2. Sync policies: automated, prune and self-heal

   An automated sync policy applies every new commit; prune deletes what was removed from Git, self-heal reverts manual changes, and sync options tune how objects are applied.

3. Sync waves and resource hooks

   Sync waves order resources inside one sync; hooks run Jobs before, during or after it — for example a database migration before the new version starts.

4. Environments, promotion and rollback

   Each environment is its own Application and folder; promotion is a pull request that copies a tested version forward, and rollback is a Git revert.