# Cgroups: A Deep Dive into Resource Management in Kubernetes — retained record

> Retained reddit record from reddit:kubernetes.

Canonical: https://highsignal.app/data/records/d1591012550084e7

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:kubernetes)  published 2026-11-03 07:25 ingested 2026-11-04 02:40

[original source ↗](https://www.reddit.com/r/kubernetes/comments/1xmmlaz/cgroups_a_deep_dive_into_resource_management_in/)

## retained text



```
You set CPU and memory requests and limits in a Kubernetes pod spec:  


    resources:
        requests:
           cpu: 500m
           memory: 256Mi
       limits:
           cpu: "1"
           memory: 512Mi
    

What happens next?  
  
Kubernetes uses requests to schedule your pod, and CPU requests also decide your share of the CPU when the node is busy. On Linux, the kubelet and container runtime set up cgroups, and the kernel enforces the limits.  
  
A CPU limit can throttle your workload. A memory limit can lead to an OOM kill when the container tries to use more than its limit and the kernel can’t reclaim enough memory. You can see the kernel’s side of the story in a few files on the node.  
  
This three-part series follows the path from your pod spec to the kernel, with diagrams and hands-on labs:

🧱 Part 1: Foundations

[https://nithinjohngeorge.com/blog/cgroups-deep-dive-kubernetes-part-1/](https://nithinjohngeorge.com/blog/cgroups-deep-dive-kubernetes-part-1/)

⚙️ Part 2: CPU

[https://nithinjohngeorge.com/blog/cgroups-deep-dive-kubernetes-part-2/](https://nithinjohngeorge.com/blog/cgroups-deep-dive-kubernetes-part-2/)

🧠 Part 3: Memory

[https://nithinjohngeorge.com/blog/cgroups-deep-dive-kubernetes-part-3/](https://nithinjohngeorge.com/blog/cgroups-deep-dive-kubernetes-part-3/)


```



document fetched 2026-11-04 00:36 · canonical https://reddit.com/r/kubernetes/comments/1xmmlaz/cgroups_a_deep_dive_into_resource_management_in
