Foundation

Argo CD

DCDR

GitOps controller per cluster — reconciles the live state of DC and DR from a single Git repo.

Quick facts

Role
Continuous delivery / drift detection
Pattern
App-of-apps (root glob fans out per-app Applications)
Source repo
infra/gitops-rke2 on the lab GitLab
Scope
DC reconciles clusters/dc/apps/; DR reconciles clusters/dr/apps/

What it is

Argo CD runs in each RKE2 cluster as the GitOps controller and is the only way changes land in the platform. The DC and DR instances both watch the same monorepo (infra/gitops-rke2) but each scopes its reconciliation to its own clusters/<dc|dr>/apps/ path, while sharing values from shared/helm-values/.

App-of-apps with a root glob means adding a new app is a single-file change: drop a YAML under the right cluster path and Argo CD picks it up.

Architecture

Add diagrams or topology notes here — how this component sits relative to DC/DR, what replicates, and what speaks to it. Mermaid blocks render as plain text today; embed images under /assets/ when needed.

Configuration

Add chart values overrides, important env vars, OIDC client config, secret references. Link to the source files in infra/gitops-rke2 rather than copying YAML wholesale — the repo is the source of truth.

Operations

Add runbook notes: backup, restore, common troubleshooting, dashboards, on-call cheatsheet entries.

Failover

Add DC/DR cutover/cutback notes: edge HAProxy backend name, healthcheck path, measured cutover/cutback times, smoke-test commands.

References