← All insightsKubernetes

Kubernetes GitOps without the hype: where ArgoCD helps, and where it doesn't

CodeWizard Engineering · 31 July 2026 · 6 min read

Every second Kubernetes blog says Git is now 'the single source of truth'. True - and misleading. GitOps (git as the declarative source for what runs in the cluster) genuinely fixes a real class of problems. Knowing which problems it fixes, and which it doesn't, decides whether your adoption succeeds or stalls.

What GitOps actually fixes

  • Configuration drift - the cluster can no longer silently diverge from what you intended, because reconciliation snaps it back
  • Unreviewed changes - every manifest change is a pull request with an audit trail
  • 'Works on my laptop' environments - one environment pipeline, applied everywhere
  • Human clicking in production UIs - the controller applies, humans review

What GitOps quietly doesn't fix

  • State and data - nobody GitOps' a database. Backup, restore and DR still need real engineering
  • Bad architecture - GitOps makes wrong architecture reproducible, not right
  • Secrets - git is for manifests, not for API keys; you still need Vault or a cloud secret manager
  • The review bottleneck - reviewers become the pipeline; if nobody understands the manifests, 'reviewed in git' is theater

The failure mode I see most isn't adoption - it's adoption-without-ownership. Teams install ArgoCD, point it at a repo, and assume the job is done. It isn't. Someone must own the app-of-apps structure, the upgrade cadence, the backup story, and what happens when a sync breaks the cluster.

A sane adoption path

  • Start with one namespace and one app-of-apps pattern, not a company-wide platform
  • Make everything deployable via git - then make deploying evil easy to revert
  • Wire secrets to Vault before day one; retrofitting secrets is painful
  • Practice the failure drills: broken sync, deleted namespace, bad upgrade
GitOps is a baseline, not a destination. It earns its keep the day something breaks - and fails you the day before, if nobody owns it.

Want a real-world look at how these decisions play out? That's a recurring topic in the K8S IL and ArgoCD IL community groups - free to join, run by our engineers, no sales pitch involved.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult