migrations/argocd-to-flux/

[giscus[bot]]

migrations/argocd-to-flux/

Migrating from ArgoCD to Flux — the why, the how, and what I learned

https://hai.wxs.ro/migrations/argocd-to-flux/

[bmillemathias]

Hi,

thanks for the thorough review. We use too fluxcd at work, we chose it over Argocd because it was lighter, and also because it has no UI where people could do changes without be traced. I'm happy for the review because I did not these flaws when we tested it.
One thing I would like to see improved is have more detailed explanations on the components and the new features on releases. Unless you are a seasoned admin, it's hard to understand the benefits.

What are the benefits to use fluxcd operator ? I did not really understood what it brings over just using fluxcd.

Best

[vtmocanu]

Glad you enjoyed the article, regarding release notes, have you checked out the Flux blog?
https://fluxcd.io/blog/

And for operator, you can get auto-updates for flux, like pin version to 2.8.x and get automatic patch upgrades, use the webUI, i think that is only availble with the operator, and use ResourceSet https://fluxoperator.dev/docs/crd/resourceset/ which I have not tried yet.

[bateller]

Hey, thanks for writing this up. Super clear, and the CRD ordering / apply sequencing issue is exactly the kind of thing teams only notice when they’re already having a bad day.

I actually featured this post on my Ship It Weekly episode this week (ArgoCD vs Flux, and the bigger “control planes fail in subtle ways” theme). If you want the audio version, it’s here: https://www.tellerstech.com/ship-it-weekly/aws-bahrain-uae-data-center-issues-amid-iran-strikes-argocd-vs-flux-gitops-failures-github-actions-hackerbot-claw-attacks-trivy-roguepilot-codespaces-prompt-injection-block-ai-remake/

[vtmocanu]

Thanks for the kind words, and that's awesome that it made it to Ship It Weekly! TBH did not know about this series, will check it out!