GitOps - Feat. Flux, Argo CD, and kapp-controller (You Choose!, Ch. 2, Ep. 2)

Choose Your Own Adventure: The Treacherous Trek to Production
In this episode, we'll figure out how to reconcile the actual state (Kubernetes resources) into the desired state stored in Git (Kubernetes manifests). This time, the choice will be between Flux, Argo CD, and Carvel kapp-controller.
#argocd #fluxcd #carvel #kubernetes
This and all other episodes are available at • You Choose .
More information about the "Choose Your Own Adventure" project including the source code and links to all the videos can be found at github.com/vfarcic/cncf-demo.
٩( ᐛ )و Whitney's KZbin Channel → / @wiggitywhitney
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬
🔗 Configure Synchronization with GitOps: github.com/vfarcic/cncf-demo/...
🎬 Flux CD v2 With GitOps Toolkit - Kubernetes Deployment And Sync Mechanism: • Flux CD v2 With GitOps...
🎬 What the Flux?! GitOps at Your Fingertips: via.vmw.com/Flux
🎬 Argo CD - Applying GitOps Principles To Manage A Production Environment In Kubernetes: • Argo CD - Applying Git...
🎬 What is Argo CD?: via.vmw.com/ArgoCD
🎬 What Is Carvel kapp-controller?: via.vmw.com/kappcontroller

[@BernhardRode]

You talked about kickstarting a "new" account. This would be a great episode, too =)

[@powersurge5576]

What I am really interested to see is the Gitops for combined resources, that includes CSP resource provisioning that is back referenced in the helm chart (akv, managed identity, storage accounts, etc.) This can be a challenging task, depending on the conditional approvals you may have on changes that are only visible at deployment time (e.g. terraform plan based approvals). Another one, resource replacement if certain property is changed in terraform. Surely there are more scenarios that you don't want to blindly deploy. You need some CI health check logic during and after deployment. Focus still should be - do not introduce outage!

[@powersurge5576]

Something I didn't hear mentioned are the rollbacks (Helm atomic upgrade equivalent) which Flux supports. It is handy for self-service and allows for OPS-free deployment recoveries.

[@mirceanton]

Thanks for answering my question about Flux/ArgoCD for admins(SRE) vs developers! I had a discussion about this with a coworker a few days back and those were some really good points. We were focusing mainly on the point Scott made, as in we considered Flux as something that just works under the hood and Argo as something that has more user-interaction due to the built-in UI.

[@itspngu]

That's precisely why I've happily been using Flux for close to 2 years now. It's a toolkit, not an all-in-one-and-then-some solution. Emphasis is put on shipping a set of components that work together, can be used individually (to some extent), and are easily integrated with other systems. Does what it says on the tin, no more, no less. Unix vibes. :) (I'm sure ArgoCD is great too, it's just not for me)

[@mirceanton]

@@itspngu Precisely! What I'm working on implementing in my Homelab right now is to automate the "platform" deployment with Flux, so all the services I want to consume on my cluster, and then for my development needs and side projects try to integrate them with Argo so I can get some hands-on experience with both tools. Just like you said, I really like the approach of Flux to simply do what's on the label and nothing else. Argo seems more of a platform/ecosystem to me whereas Flux is a tool.