<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Karthik B Hegde | DevOps Engineer</title><link>https://karthikhegde.in/tags/kubernetes/</link><description>Recent content in Kubernetes on Karthik B Hegde | DevOps Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Karthik B Hegde</copyright><lastBuildDate>Tue, 11 Aug 2026 03:00:00 +0530</lastBuildDate><atom:link href="https://karthikhegde.in/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Synced and Healthy: The Six-Day Outage Every Dashboard Reported as Fine</title><link>https://karthikhegde.in/blog/grafana-wedged-sqlite/</link><pubDate>Tue, 11 Aug 2026 03:00:00 +0530</pubDate><guid>https://karthikhegde.in/blog/grafana-wedged-sqlite/</guid><description>&lt;p&gt;For six days &lt;code&gt;grafana.karthikhegde.in&lt;/code&gt; returned 502.&lt;/p&gt;
&lt;p&gt;For those same six days ArgoCD reported the monitoring application as &lt;strong&gt;Synced&lt;/strong&gt; and &lt;strong&gt;Healthy&lt;/strong&gt;. Kubernetes reported the Grafana pod as &lt;strong&gt;Running, 1/1, zero restarts&lt;/strong&gt;. And the fix — the correct fix, the one that would have resolved this in about sixty seconds — had been committed to the repository three weeks earlier.&lt;/p&gt;
&lt;p&gt;None of those three facts is a bug on its own. Together they describe a platform that had no mechanism left to tell me it was broken.&lt;/p&gt;</description></item></channel></rss>