<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes (Helm) on Netdata</title><link>https://www.netdata.cloud/tags/kubernetes-helm/</link><description>Recent content in Kubernetes (Helm) on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 05:09:03 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/kubernetes-helm/index.xml" rel="self" type="application/rss+xml"/><item><title>Fix Helm Chart Rollback &amp; Pending-Upgrade Failures</title><link>https://www.netdata.cloud/academy/helm-chart-rollback-failures/</link><pubDate>Fri, 15 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/helm-chart-rollback-failures/</guid><description>&lt;p&gt;It’s a scenario that every Kubernetes operator dreads. A production deployment has gone wrong, you confidently initiate a Helm rollback, and then&amp;hellip; nothing. The command hangs, and a quick check reveals the dreaded &lt;code&gt;pending-rollback&lt;/code&gt; status. Your application is now in a broken state, and you&amp;rsquo;re blocked from deploying any new fixes. This is more than a minor inconvenience; it&amp;rsquo;s a critical failure that can leave your services unstable and your deployment pipeline paralyzed.&lt;/p&gt;</description></item><item><title>Monitoring without Cooperation: Kubernetes</title><link>https://www.netdata.cloud/blog/monitoring-without-cooperation-kubernetes/</link><pubDate>Fri, 20 May 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/monitoring-without-cooperation-kubernetes/</guid><description>&lt;!--truncate--&gt;&#10;&lt;iframe width="560" height="315" src="https://www.youtube.com/embed/J2kdSTRJzV4?si=Rqv4gpqz_wZKusaZ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen&gt;&lt;/iframe&gt;&#10;&lt;p&gt;Imagine this: You are an engineer at a startup. You are responsible for keeping all the applications running smoothly and safely in production. At first, you have things under control, but soon enough things start getting more complex. The system has grown by hundreds of new server nodes, new services and containers are showing up seemingly every day, and you hear there’s a project to transition everything to Kubernetes (you’ve heard the term “cloud native” so often that the phrase shows up in your dreams).&lt;/p&gt;</description></item></channel></rss>