https://k-s-pavan-kumar.github.io/hugo-nimbus/tags/ci-cd/Recent content in Ci-Cd on NimbusHugoen-usSat, 01 Jun 2024 00:00:00 +0000https://k-s-pavan-kumar.github.io/hugo-nimbus/adr/0002-gitops-cluster-config/Sat, 01 Jun 2024 00:00:00 +0000https://k-s-pavan-kumar.github.io/hugo-nimbus/adr/0002-gitops-cluster-config/<h2 id="context">Context</h2> <p>Cluster configuration changes currently happen via direct <code>kubectl apply</code> from engineer laptops. We have no audit trail and drift between clusters is common.</p> <h2 id="decision">Decision</h2> <p>Adopt a GitOps workflow (Argo CD) where the Git repository is the single source of truth for cluster state, and all changes go through pull request review.</p> <h2 id="consequences">Consequences</h2> <ul> <li>Every config change is reviewable and revertible via Git history.</li> <li>Emergency changes need a documented break-glass procedure, since direct <code>kubectl apply</code> will be restricted in production namespaces.</li> <li>Requires migrating ~40 existing manifests into the GitOps repo before enforcement can begin.</li> </ul>