DevOps & cloud native
Kubernetes, CI/CD, infrastructure as code and observability. For engineers who build and run production systems.
About this list
The selected sources include Blog – Cloud Native Computing Foundation, Kubernetes Blog, Docker. Open each item at its original source for the complete article, episode or video. This is a selection of current coverage, not a complete archive.
Stories from Kubernetes Blog. Show all stories · All sources
Latest stories
Newest first
Updates are delayed. Showing the last checked articles.
Why Is My Kubernetes Job Still Pending? Tracing Kueue Admission with Headlamp
You submit a Kubernetes Job and wait for its Pods to appear. A minute passes. Then another. The Job is still suspended, there are no application logs, and there may not even be a Pod to inspect. In a cluster managed by Kueue, this can be completely normal. Kueue may still be deciding whether the Job can use the requested resources. The useful question is not only “Why is the Pod pending?” It is first “Has Kueue admitted the Workload?”
The Shift to cgroup v2 in Kubernetes: What You Need to Know
In Linux, cgroups (control groups) are a kernel feature used for managing system resources. Kubernetes uses cgroups to allocate resources like CPU and memory to containers, ensuring that applications run smoothly without interfering with each other. With the release of Kubernetes v1.31, support for v1 cgroup management moved into maintenance mode.
Scaling Kubernetes Workloads with Node Swap
Memory is often the first hard limit a Kubernetes cluster hits. Nodes run out of RAM long before they run out of CPU, and the new wave of agentic AI workloads makes this worse. These workloads demand large memory footprints to start up and run untrusted code, then sit idle waiting for the next prompt. That idle but resident memory is expensive, and it caps how many pods a node can hold. This is where swap helps.
You have reached the end of this list.
Showing 3 of 3 articles
Know a source we’re missing? Tell us about it