Multi-Stage Deployment Pipelines the GitOps Way - Jesse Suen & Kent Rancourt, Akuity

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon Europe in Paris from March 19-22, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
Multi-Stage Deployment Pipelines the GitOps Way - Jesse Suen & Kent Rancourt, Akuity
In the pursuit of ever-faster and more-frictionless application delivery, GitOps excels at continuous delivery to single environments. Yet leading, open-source GitOps platforms offer little to accommodate modern deployment pipelines that span many stages, regions, and clouds, and may involve lengthy verification processes. These missing features often force GitOps practitioners to inappropriately fall back on CI platforms and bespoke automation, resulting in complex and fragile deployment pipelines. This talk will zero in on an alternative: patterns that address these challenges while remaining true to established GitOps principles - and an emerging open-source implementation of those patterns. Kargo promises to address these challenges in a declarative fashion while complementing GitOps practitioners’ current crop of favorite tools, such as Kustomize, Helm, Argo CD, and Flux.

[@arjan8436]

Looks great! The missing release orchestration UI is often a problem for many people in different roles working on a Argo/Gitops deployed project. I currently don't see how you would model a Project which consists of more than a single Pipeline without having to duplicate the same Stage definitions for every Pipeline. Maybe I expected a Pipeline definition to have an explicit crd and bind stages or a pipeline template to it. I will wait for a bigger example project on how to deploy multiple apps with Kargo 🙂

[@yoprstification]

Commits during a deploy do not look safe for me. What about parallel deploys somebody else might be doing?

[@mfreeman451]

good stuff, thank you

[@TheALEXiSounds]

Going to look more into this, but immediately turned off by the need to just rename things for no reason. Just call it an artifact. Freight is horrible.