<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Helm on Danilo Falcão da Silva</title><link>https://falcao.org/tags/helm/</link><description>Recent content in Helm on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 19 May 2026 13:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/helm/index.xml" rel="self" type="application/rss+xml"/><item><title>Helm 4 Made Me Stop Looking for an Alternative</title><link>https://falcao.org/posts/helm-4/</link><pubDate>Tue, 19 May 2026 13:00:00 -0300</pubDate><guid>https://falcao.org/posts/helm-4/</guid><description>&lt;p>Helm has been the punchline of Kubernetes packaging for about as long
as Kubernetes has been called Kubernetes. Helm 2 had &lt;strong>Tiller&lt;/strong>, an
in-cluster component running as cluster-admin that read every chart&amp;rsquo;s
YAML and applied it from inside the cluster — a security horror show
that drove half the community to invent its own deployment tooling
just to avoid it. Helm 3 finally killed Tiller in 2019 and went
client-side, which fixed the worst of it. And then Helm 3 sat there,
relatively unchanged, for &lt;strong>six years&lt;/strong>.&lt;/p></description></item></channel></rss>