Have your GitOps cake and eat it too.

It's been nearly 6 years since I first heard the word "GitOps", a term used to describe a set of best practices born out of using developer tooling to drive operations ("Ops") teams. Weaveworks, the company I mostly associate as the inventors of GitOps, has a great primer for anyone unfamiliar with the topic that wants to learn more about GitOps as a practice. More notably, they released a GitOps tool this week called Flamingo that settles an age old question for Kubernetes operators - which GitOps tool do you choose: Flux or ArgoCD? Operating Kubernetes infrastructure and applications at scale requires the adoption of best practices that are inextricably joined at the hip with the GitOps mindset; platform teams absolutely need to practice GitOps, or risk falling down on their face.

Every tool comes with tradeoffs, and until the Weaveworks announcement this week, many platform engineering teams were forced to choose. As someone who started out using Flux, and then pivoted to ArgoCD, I'm excited to see how Flamingo integrates the best of both worlds. Teams invest significant time and energy adopting tools and platforms, and don't take the decision to move away from them lightly. I hope you'll stay tuned and follow along as I demonstrate some of the things I've found ArgoCD does really well, examine some of the use-cases that it struggles with, and how you can have your cake and eat it too by leveraging your existing investment in ArgoCD, but extending it through Flux and Flamingo.