Hacker News Reader

ArgoCD is meh. Its a UI over your k8s clusters. What happened to us is sre/devops types just use k9s or the console. The devs could not be bothered to log into argo. They just merge, and code gets deployed. They don't hang out on argo. With 5k+ pods, the UI doesn't even work. So it isn't designed for large systems which makes it further weird.

View on HN

> Its a UI over your k8s clusters.

Not really. It's a deployment tool, the UI is there to help see what's happening with deployments. It's not intended to be a primary interface to cluster management the way k9s or Lens etc. is.

> They just merge, and code gets deployed.

How does "code get deployed" though? There has to be something that's actually (1) monitoring branches and (2) running the equivalent of `kubectl apply` to deploy manifests. That's what ArgoCD does.

If you're saying devs are using k9s or kubectl to manually trigger the apply from a branch, that has all sorts of drawbacks, which is exactly what Argo is designed to address.

Reply on news.ycombinator.com