At 14:17 UTC on March 12, 2024, a single Kubernetes 1.32 node in our production EU-West-1 cluster hit an OOM (Out-Of-Memory) threshold that triggered 23 minutes of cascading pod evictions, dropped 14% of real-time user traffic, and cost $42k in SLA penalties before we stabilized the control plane.

🔴 Live Ecosystem Stats

⭐ kubernetes/kubernetes — 121,985 stars, 42,943 forks

Data pulled live from GitHub and npm.

📡 Hacker News Top Stories Right Now

Ghostty is leaving GitHub (576 points)

OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOs (63 points)

A playable DOOM MCP app (55 points)

Warp is now Open-Source (90 points)

Waymo in Portland (168 points)

Key Insights

Kubernetes 1.32's kubelet memory accounting for containerd 2.0.0-rc.1 undercounts shared page cache by 18-22% in high-IOPS workloads, leading to silent OOM risks.

The default node-problem-detector v0.8.12 shipped with Kubernetes 1.32 has a 90-second delay in reporting OOM events to the control plane, masking…