Repositories

Boundaries

PathRoleNotes
lab-gitops/Platform desired stateOperators, storage, ACM, OADP, service mesh, ESO wiring, policies, dashboards, cluster overlays, and platform cleanup commits.
lab-workloads/Application workload sourceNon-platform app bases. Source-only bases are inert until a cluster overlay references them.
lab-gitops/Bootstrap contextBootstrap-only reference copied from ocp-bootstrap. Do not treat it as the live desired-state source.

Argo CD

Recorded app model

Root app

Root application on hub-dc reconciles the platform repo and ApplicationSets.

Cluster config apps

Each cluster has a cluster-config Application. Local spoke Argo status is authoritative for managed-pull spoke apps.

Workload app

hub-dc-workloads points at lab-workloads and deploys only referenced workload overlays. The ApplicationSet matches spoke-dc only — spoke-dr is platform standby (decision 2026-05-07) and opts in deliberately via the activation runbook. Workload Applications use traditional push-based delivery (hub Argo on hub-dc registers spoke-dc as a destination cluster and pushes via RHACM cluster-proxy) per ADR-0006, which supersedes ADR-0003 for the POC. Argo CD Agent is the documented future-migration path.

Current repo facts

Recent boundaries enforced

Validation

Expected checks after changes

oc kustomize lab-gitops/clusters/hub-dc
oc kustomize lab-gitops/clusters/hub-dr
oc kustomize lab-gitops/clusters/spoke-dc
oc kustomize lab-gitops/clusters/spoke-dr
oc kustomize lab-workloads/clusters/spoke-dc
oc kustomize lab-workloads/clusters/spoke-dr

For live validation, check Argo CD sync and health on the specific cluster that owns the Application. Avoid assuming the hub-side status artifact is authoritative for managed-pull spokes.