<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Continuous Delivery on rtnpro</title><link>https://rtnpro.com/tags/Continuous-Delivery/</link><description>Recent content in Continuous Delivery on rtnpro</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 31 Jul 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://rtnpro.com/tags/Continuous-Delivery/index.xml" rel="self" type="application/rss+xml"/><item><title>Why We Built on Argo CD and Kargo Instead of Reinventing CD</title><link>https://rtnpro.com/post/2026-07-31-why-argocd-and-kargo/</link><pubDate>Fri, 31 Jul 2026 09:00:00 +0530</pubDate><guid>https://rtnpro.com/post/2026-07-31-why-argocd-and-kargo/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;For three weeks I&amp;rsquo;ve ended every post with the same claim and never once shown my work.&lt;/p&gt;
&lt;p&gt;The claim: the CNCF ecosystem already solved continuous delivery, and what the mid-market team is missing isn&amp;rsquo;t technology, it&amp;rsquo;s the &lt;em&gt;assembly&lt;/em&gt; — a golden path stitched from primitives that already exist. Argo CD reconciles. Kargo promotes. The last post argued you should adopt that road as a product rather than build it as a project.&lt;/p&gt;</description></item></channel></rss>