Architecture
Patterns, not internal runbooks
How a real GitOps catalog is organized. Original writing — no customer manifests, no product names.
- 01 GitOps flow CI builds the image. Git records the tag. The cluster syncs. Nobody applies manifests by hand. Read
- 02 Overlay model Generic base, per-environment overlay. The diff between dev and prod should fit in a review. Read
- 03 Many clusters, one catalog Cloud, on-prem, and lab Kubernetes in the same repo. The destination changes; the model does not. Read
- 04 Helm-in-Kustomize The chart arrives at sync time, not in Git. Kustomize names the chart; Argo CD fetches it. Read
- 05 Gateway API, TLS, and DNS Hostname and certificate are platform concerns. The app only exposes a Service. Read
- 06 Observability Metrics, logs, and cost as GitOps components. One surface. Many destinations. Read
- 07 What never goes in Git The catalog is visible to the team. Credentials, chart cache, and kubeconfig are not. Read