#kubernetes (2024-10)
Archive: https://archive.sweetops.com/kubernetes/
2024-10-10
Does anyone have any good resources on the considerations between having an ArgoCD instance per cluster vs a single ArgoCD orchestration instance for multiple clusters? I found this vid. https://www.youtube.com/watch?v=bj9qLpomlrs
I’ve heard once that someone tried to delete argo deployed “accidentally” into the default namespace, which in turn messed up entire cluster.
Not sure does it fit into discussion, but maybe worth to think something along those lines. And what about separation of lifecycle between prod and non-prod environments?
Too funny. The more people hype this magical kit, the more it looks exactly the same as everything else. It’s not like those external influences to your internal operational mandates are changing – re: availability, reliability, security, compliance, vendor evaluations, etc.
Pretty much yeah. Despite this, I think I will go down this road ‘cause I need those Argo features like canary releases, instrument releases/lifecycle with running e2e testing even before merging to master, running them again after release - and some other tests, rollbacks, custom workflows etc
It’s fine. Enough retrospectives get folks into shape over time. Leaning on learned lessons and industry standards isn’t important. I love an innovator, but that activity belongs in the application layer, not anywhere near ops reliability concerns.
The thought of having an argo per LOB/Business driven separation of concern isn’t bad.