Kubernetes Workloads
posts (4)
- CPU in Kubernetes from the kernel up8/12
Why 1 CPU does not mean one core
CPU time and CPU placement are two different mechanisms. A limit says how much you may consume; affinity and cpuset say where a task may execute.
- CPU in Kubernetes from the kernel up7/12
Requests, Limits and QoS: how Kubernetes classifies Pods
A QoS class is the result of how requests and limits are configured, not a separate CPU allocation mechanism. Guaranteed is not a dedicated core.
- CPU in Kubernetes from the kernel up4/12
CPU Limits and throttling: what a CPU limit really does
A limit does not pin a container to a core. It gives it a CPU-time budget accounted per period, and once that runs out the kernel throttles it.
- CPU in Kubernetes from the kernel up3/12
CPU Requests in Kubernetes: what they really are
A request is a declaration of demand, not a ceiling. It feeds placement in kube-scheduler and CPU weight on the kernel side.