Managing a Fleet of Clusters Without Losing Track of Reality
From 2 clusters to 20: kubeconfig hygiene, fleet-wide visibility, and GitOps per cluster. The patterns that keep multi-cluster from becoming multi-chaos.
Read the postPosts tagged "gitops"
10 posts about gitops in the conndeck blog — field notes on local-first Kubernetes operations, GitOps, and production debugging.
ArgoCD vs Flux: After Running Both in Production
An honest ArgoCD vs Flux comparison from someone who ran both in production: install, day-two ops, multi-tenancy, drift handling, and which one I'd pick when.
Read the postExternal Secrets Operator: Stop Committing Secrets
Why encrypted secrets in git still lose, and how to wire External Secrets Operator to Vault or a cloud secret manager with rotation that actually works.
Read the postPromoting Between Environments in GitOps Without Losing Your Mind
How to promote from staging to prod in GitOps: repo layouts, Kustomize overlays, image tag promotion via PR, and the habits that prevent drift.
Read the postHelm vs Kustomize: An Honest Take From Both Sides
Helm vs Kustomize without the tribalism: templating vs overlays, release management vs GitOps, drift behavior, and how I use both on the same cluster.
Read the postArgoCD ApplicationSets: Stop Copy-Pasting Your Environments
Hand-maintaining near-identical ArgoCD Application manifests per cluster is a slow-motion incident. Here's how ApplicationSet generators fix it, and where they bite back.
Read the postArgoCD Sharding, Reconciliation Tuning, and the 1,000-App Wall
What actually breaks when ArgoCD grows past hundreds of Applications: controller sharding, reconciliation tuning, repo-server memory, and the metrics to watch.
Read the postArgoCD Sync Waves: Ordering Your Deploys Without Losing Your Mind
A practical guide to ArgoCD sync waves: why resource ordering matters, how the sync-wave annotation really works, and the mistakes that bite everyone.
Read the postGitOps Is a Discipline, Not a Tool
Installing ArgoCD doesn't make you a GitOps shop. Here's why the tool changes nothing until the team agrees to stop running kubectl apply from their laptops.
Read the postkubectl apply Is Lying to You (and What to Do About It)
kubectl apply says 'configured' and you believe it. Here's why declared YAML and real cluster state drift apart, and how to actually close the loop.
Read the post