Rollback in GitOps Is Simple Only When Releases Are Identifiable
Connecting Git reverts, ArgoCD reconciliation, and immutable artifacts into one recovery model.
Connecting Git reverts, ArgoCD reconciliation, and immutable artifacts into one recovery model.
Turning the current single-destination pattern into an environment promotion model.
The moment Git stopped being a storage location for YAML and became the source of intended runtime state.
A deterministic path from Application source to rendered chart to Kubernetes object to runtime process.
The difference between desired-state convergence and application correctness.
What drift is, how reconciliation changes it, and when a manual change is a warning sign.
What the current ArgoCD destination implies and what I would revisit as environments grow.
How ArgoCD finds the intended service definition inside the repository.
Using an apps directory for Helm packages and an argocd directory for deployment controllers.
Why deleted desired-state resources should not silently live forever in the cluster.
The benefits and costs of independently reconciling each major workload.
A mental model for separating deployment control from application traffic and background work.
The difference between having Kubernetes manifests and having a repeatable delivery system.
Breaking down repository source, chart path, destination cluster, namespace, and sync policy.
The trade-off of following the current branch head rather than pinning a release revision.
The difference between correcting resource drift and fixing a broken application.
Moving from imperative deploy commands to controller-driven convergence.