<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Keel - Tag - vo.rs</title><link>https://vo.rs/tags/keel/</link><description>Keel - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 24 Oct 2024 10:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/keel/" rel="self" type="application/rss+xml"/><item><title>Keel: Automated Kubernetes Deployments Without GitOps Overhead</title><link>https://vo.rs/story/keel-automated-kubernetes-deployments-without-gitops-overhead/</link><description>&lt;p&gt;The orthodox answer to &amp;ldquo;how should my Kubernetes cluster deploy updates&amp;rdquo; is GitOps: Argo CD or Flux watching a Git repository, reconciling the cluster to match declared state, the whole pull-based pipeline. It is genuinely the right answer for a team shipping a product. For a homelab cluster running Sonarr, a couple of dashboards, and the odd hobby project, it is also a small mountain of YAML, a controller to babysit, and a Git workflow you have to actually follow. Sometimes you just want third-party images to update themselves when a new tag lands, without standing up a GitOps engine to do it.&lt;/p&gt;</description><pubDate>Thu, 24 Oct 2024 10:00:00 +0000</pubDate></item></channel></rss>