<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitops on Jeff Bilder</title><link>https://jeffbilder.com/tags/gitops/</link><description>Recent content in Gitops on Jeff Bilder</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 28 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jeffbilder.com/tags/gitops/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing a GitOps Pipeline That Survives 3am</title><link>https://jeffbilder.com/post/designing-a-gitops-pipeline/</link><pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate><guid>https://jeffbilder.com/post/designing-a-gitops-pipeline/</guid><description>The best compliment a deploy pipeline can get is silence. Nobody Slacks about it. Nobody &amp;ldquo;just kicks off the build.&amp;rdquo; It runs because someone merged a pull request, and the system quietly makes reality match the repo.
That&amp;rsquo;s the whole idea behind GitOps, and it&amp;rsquo;s less about tooling than it is about a single rule: the desired state of your system lives in git, and a machine — not a human — is responsible for closing the gap between git and production.</description></item></channel></rss>