This case study traces a 503 at the ingress back to a broken CNI overlay between nodes, even though every pod and endpoint looked healthy, and fixes it with topology spread constraints.
More: https://ku.bz/M-PjSd6Tl
Post #4039
308
- Sep 23, 2026This article lays out a GitOps reference architecture for running one app across 25 region…
- Sep 23, 2026This week on Learn Kubernetes Weekly 202: 🔥 We Replaced etcd with Google Cloud Spanner 😌…
- Sep 22, 2026This tutorial shows how to chain KEDA cron scaling with Karpenter so non-prod EKS clusters…
- Sep 21, 2026This article explains how to make Kubernetes spend traceable to each team, using a consist…
- Sep 21, 2026Rune is a fast native macOS app for people who debug clusters every day, with unified pod…
- Sep 21, 2026This case study shares a production Strimzi Kafka setup that survives broker and zone fail…