<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cari Lynn on Carvel</title><link>https://deploy-preview-832--carvel.netlify.app/blog/tags/Cari-Lynn/</link><description>Recent content in Cari Lynn on Carvel</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 23 Feb 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-832--carvel.netlify.app/blog/tags/Cari-Lynn/index.xml" rel="self" type="application/rss+xml"/><item><title>Continuous delivery using a Carvel ytt Argo CD plugin</title><link>https://deploy-preview-832--carvel.netlify.app/blog/argocd-carvel-plugin/</link><pubDate>Wed, 23 Feb 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-832--carvel.netlify.app/blog/argocd-carvel-plugin/</guid><description>Argo CD is a declarative, GitOps, continuous delivery tool for Kubernetes. It&amp;rsquo;s design embraces GitOps philosophy of using Git as a single source of truth for the desired state of the system. In this example we&amp;rsquo;re storing desired application state in ytt templates, and extending Argo CD to template and deploy them.
At a high level a deployment using Argo CD starts with a configuration change. A commit with a change is made to the application repository, causing the Argo CD controller to notice the desired state has changed.</description></item></channel></rss>