Argo Rollouts: Canary Deploys Without a Platform Team
A practitioner's guide to Argo Rollouts: canary steps, AnalysisTemplates with Prometheus metrics, aborts and rollbacks, and the gotchas that bite small teams.
Read the post8 posts about argocd in the conndeck blog — field notes on local-first Kubernetes operations, GitOps, and production debugging.
A practitioner's guide to Argo Rollouts: canary steps, AnalysisTemplates with Prometheus metrics, aborts and rollbacks, and the gotchas that bite small teams.
Read the postAn 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 postHow 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 postHand-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 postWhat actually breaks when ArgoCD grows past hundreds of Applications: controller sharding, reconciliation tuning, repo-server memory, and the metrics to watch.
Read the postA 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 postInstalling 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 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