<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title/><link>https://www.niteshchauhan.xyz/</link><description>Recent content on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 11 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.niteshchauhan.xyz/index.xml" rel="self" type="application/rss+xml"/><item><title>From $25K to $5K/Month: Running a Production Elasticsearch Cluster on Kubernetes</title><link>https://www.niteshchauhan.xyz/posts/elasticsearch/</link><pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.niteshchauhan.xyz/posts/elasticsearch/</guid><description>&lt;hr&gt;
&lt;h2 id="1-the-problem"&gt;1. The Problem&lt;/h2&gt;
&lt;p&gt;In early 2022, we were running our entire observability stack on Elastic Cloud. It was the obvious choice at the time — managed, hands-off, no operational burden. Except it wasn&amp;rsquo;t hands-off at all.&lt;/p&gt;
&lt;p&gt;The cluster was regularly falling over. OOM kills on data nodes, indexing rejections during peak load, CPU spiking to saturation with no clear root cause. We were opening support tickets with Elastic, waiting days for responses, and getting back generic JVM tuning suggestions that changed nothing. Meanwhile the bill sat at $25,000 per month.&lt;/p&gt;</description></item></channel></rss>