Delivery EngineeringAdvanced9 submodules

GitOps with Argo CD and Flux

Operate Kubernetes desired state through reviewed Git manifests and in-cluster Argo CD or Flux reconciliation with sync, health, drift detection, and recovery controls.

How this module works

From concept to production evidence

Build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Learning outcomes

Explain declarative GitOps principles
Compare Argo CD and Flux operating patterns
Structure application manifests and promotion
Configure sync and drift detection
Use automated reconciliation safely with AKS

Flow diagram

GitOps with Argo CD and Flux end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

01
Build artifactGitOps with Argo CD and Flux stage 1: build artifact with an auditable result before the next stage begins.
02
Update desired state in GitGitOps with Argo CD and Flux stage 2: update desired state in git with an auditable result before the next stage begins.
03
Review and mergeGitOps with Argo CD and Flux stage 3: review and merge with an auditable result before the next stage begins.
04
Controller detects changeGitOps with Argo CD and Flux stage 4: controller detects change with an auditable result before the next stage begins.
05
Sync and assess healthGitOps with Argo CD and Flux stage 5: sync and assess health with an auditable result before the next stage begins.
06
Detect drift and reconcileGitOps with Argo CD and Flux stage 6: detect drift and reconcile with an auditable result before the next stage begins.

Integrated hands-on lab

Adopt GitOps for AKS environments

Create environment configuration repository
Install and scope a controller
Deploy by image digest
Configure sync, health, and drift alerts
Test rollback and break-glass reconciliation

Complete module contents

9 full submodule notes

Read in order

GitOps principles

GitOps principles governs how a request is named, addressed, routed, filtered, transported, protected, and delivered to a healthy endpoint within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Declarative infrastructure

Declarative infrastructure provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Argo CD

Argo CD provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Flux

Flux provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Application manifests

Application manifests provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Sync

Sync moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Drift detection

Drift detection provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

Automated reconciliation

Automated reconciliation provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes

GitOps with AKS

GitOps with AKS moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within GitOps with Argo CD and Flux. It is not an isolated definition: its value appears when it supports build immutable artifacts separately, update environment state by reviewed commit, let a least-privilege controller pull and reconcile, observe drift, and use a documented break-glass process that returns the cluster to declared state.

Open full notes