Feed
Pro
Search

Sign in
Darkshift - a dark factory for software Bug0 - The AI-native e2e QA regression testing The foreword by Hashnode - official blog from the Hashnode team Passmark - The open-source AI framework for regression testing Hashnode gql skill - let your AI agent publish to your Hashnode blog Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

@prateeksrivastav598

Prateek Srivastava

@prateeksrivastav598·Bangalore, India·Joined August 2026

SRE & DevOps Engineer | Kubernetes, Multi-Cloud, Linux | Writing about real production systems

About

SRE & DevOps Engineer with hands-on experience managing multi-cloud Kubernetes environments across AWS, Azure, and GCP. I write about real production problems — Kubernetes troubleshooting, Ansible automation, incident response, Docker, Jenkins, and Linux. Based in Bangalore. Everything here comes from actual production systems, not tutorials.

Available for

Nothing here yet.

Prateek Srivastava's blogs

The SRE Dispatchprateeksrivastav598.hashnode.dev2 posts

About

SRE & DevOps Engineer with hands-on experience managing multi-cloud Kubernetes environments across AWS, Azure, and GCP. I write about real production problems — Kubernetes troubleshooting, Ansible automation, incident response, Docker, Jenkins, and Linux. Based in Bangalore. Everything here comes from actual production systems, not tutorials.

Available for

Nothing here yet.

Prateek Srivastava's blogs

The SRE Dispatchprateeksrivastav598.hashnode.dev2 posts

Articles Comments

Recently published

PSPrateek Srivastavainprateeksrivastav598.hashnode.dev·1d ago · 8 min read

I Managed Kubernetes Across AWS, Azure, and GCP Simultaneously — Here's What Nobody Tells You"

The day the same Helm chart behaved differently on three clouds in the same hour was the day I stopped trusting "cloud-agnostic" as a real thing. Nobody plans to manage Kubernetes on three clouds at t

PSPrateek Srivastavainprateeksrivastav598.hashnode.dev·2d ago · 9 min read

Our EKS Node Crashed and Four Auto-Recovery Mechanisms All Failed. Here's Why.

⚡ TL;DR: An EKS worker node running 30+ pods crashed at 08:43 IST on Aug 16. EC2 Auto Scaling didn't act. EKS Node Auto Repair was never enabled. Cluster Autoscaler had no headroom (Min=Max=6). Our me