This article explains how Kubernetes 1.36 moves scheduling toward whole workloads with the new PodGroup API, so AI and batch jobs get all their pods placed together instead of one by one.
More: https://ku.bz/w1nVq3D0l
Post #4001
638
- Sep 25, 2026This case study explains how Modelplane was built entirely as a Crossplane configuration,…
- Sep 25, 2026This case study shows how a team ran one Kafka cluster stretched across three separate Kub…
- Sep 24, 2026This case study shows how a payments company rebuilt deployments around GitOps with Argo C…
- Sep 24, 2026This case study shows how to migrate from fragile EC2-based infrastructure to AWS EKS with…
- Sep 24, 2026This case study shows how a nightly export job kept getting OOM-killed on Kubernetes, and…
- Sep 23, 2026This case study shows how one engineer built k8s-rightsizer in four days and cut Kubernete…