<story><title>Kargo, a multi-stage application lifecycle orchestrator</title><url>https://akuity.io/blog/introducing-kargo/</url></story><parent_chain></parent_chain><comment><author>rjzzleep</author><text>I&amp;#x27;ve used Flux, Flux2 and Argo for GitOps, and they all had their quirks. In general it seems that most CloudNative projects were kinda set in their own vision with very opinionated devs and a lot of corner cases that are not accounted for and won&amp;#x27;t be accounted for.&lt;p&gt;I have a little bit of hope that this one is going to be different with the lessons they got from Argo, but I&amp;#x27;m not holding my breath.&lt;p&gt;Ps. when I first saw Argo, I thought this is it. The solution to all my problems.</text></comment>
<story><title>Kargo, a multi-stage application lifecycle orchestrator</title><url>https://akuity.io/blog/introducing-kargo/</url></story><parent_chain></parent_chain><comment><author>abuckenheimer</author><text>I&amp;#x27;ve only skimmed the quickstart docs &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;kargo.akuity.io&amp;#x2F;quickstart&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;kargo.akuity.io&amp;#x2F;quickstart&amp;#x2F;&lt;/a&gt; but this snippet immediately clicks for me as something that I&amp;#x27;d want to try&lt;p&gt;&lt;pre&gt;&lt;code&gt;    cat &amp;lt;&amp;lt;EOF | kubectl apply -f -
    apiVersion: kargo.akuity.io&amp;#x2F;v1alpha1
    kind: Promotion
    metadata:
      name: prod-to-${FREIGHT_ID}
      namespace: kargo-demo
    spec:
      stage: prod
      freight: ${FREIGHT_ID}
    EOF

&lt;/code&gt;&lt;/pre&gt;
Have enjoyed using argo in general in the past, its got a great model for k8s native workflows &amp;#x2F; events but never got to using it for CD.</text></comment>