When /var/tmp forgot our Kafka directoryThe alert wasn’t dramatic. REST on 8083 answered fine, the connector showed RUNNING, and then I pulled task status and saw FAILED with a stack trace long enough to scroll past three screens. Patch nig6 min read·mriduliti.hashnode.devOct 11
When the cluster looked idle but nothing would scheduleThe first thing I checked was the obvious one: CPU. Our non-prod EKS workers are Karpenter-managed, and application pods had been sitting in Pending long enough that Istio and app syncs were backing u6 min read·mriduliti.hashnode.devOct 4
Patch night wasn’t one incident — it was three failure modes in a rowTuesday’s plan looked boring on paper: run the SSM patch runbooks across a bunch of Auto Scaling Groups, bake AMIs, promote launch templates, go home. By midnight I was still on a call with Jenkins co9 min read·mriduliti.hashnode.dev2ISep 27
No official Storm Helm chart — how we put Apache Storm on EKS anywayThe Argo CD app for Storm had been red for two days, but the symptom that actually sent me down the rabbit hole was quieter than a crash loop: init containers on the Supervisor pods, stuck forever, pr10 min read·mriduliti.hashnode.devSep 17
We tagged EKS workers like app servers — and Prometheus started scraping telegraf on nodes that never had itThe Telegraf Down alerts started piling up on a Thursday morning, and at first glance it looked bad. Nine targets, all critical, all under the same rule name. My first instinct was a fleet-wide agent7 min read·mriduliti.hashnode.devSep 12