ArgoCD

Most teams treat audit evidence as paperwork they assemble after the fact. With GitOps the evidence is a side effect of how you already deploy. This post explains GitOps in plain terms, why a signed and reviewed change history is stronger proof than a ticket, and how to handle the two cases that still break it: emergency changes and drift.

With Talos, Cilium, Linstor, and cert-manager in place, the cluster has infrastructure but no principled way to operate it. This post adds GitOps: FluxCD for the foundation layer where ordering and simplicity matter, ArgoCD for the application layer where a UI and per-project scoping matter more. The bootstrap sequence that hands control from a script to a Git repo, the self-management property that follows, and what GitOps does not tell you about developing against it.

Implementation guide for creating an ArgoCD cluster that manages its own configuration and updates through GitOps, including repository structure, app-of-apps pattern, and self-healing configuration.