Re:We built the fastest CI in the world and it failed
by psYchotic on Tuesday September 12, 2023 @04:45PM
(#37488018)
Isn't ArgoCD more of a GitOps tool? The pretty UI is mostly secondary to its main purpose for me, which is to keep the declarative "truth" in source control, and have ArgoCD be the control loop that keeps the cluster in sync with that truth. Accidentally nuked namespace? No worries, ArgoCD's (or whatever alternative, like flux) got your back!
[ Parent
| on HN ]
Re:We built the fastest CI in the world and it failed
by rrrix1 on Tuesday September 12, 2023 @05:54PM
(#37489061)
Exactly this. The critical difference being who deploys and when/how your resources are deployed - a human, or a machine.
Having git be the source of truth of your production environment is a blessing and a curse which is directly related to the maturity of the deployment system.
If you have low confidence in your deployments (as in, you don't deploy very often and don't have full e2e tests & monitoring), GitOps is nightmarishly scary compared to classic, battle tested Ops team CLI scripts.
Re:We built the fastest CI in the world and it failed
by gabereiser on Tuesday September 12, 2023 @10:04PM
(#37491321)
I don’t accidentally do anything in production. Sorry. Nor do my teams or any developers who have access to my clouds. These kinds of failures don’t happen in my world. You will not have a mutable environment outside of data storage. Period. Nuke all you want, it will repair and redeploy itself.