Kubernetes Resource Limits: Memory vs CPU (Quick Insight)
When a container exceeds its resource limits, Kubernetes handles memory and CPU very differently:
๐ด Memory Limit Exceeded
- Pod is OOMKilled (Out Of Memory)
- Container is terminated immediately
- Reason: Memory is not compressible โ system must free it
๐ก CPU Limit Exceeded
- Pod is NOT killed
- CPU usage is throttled
- Container runs slower but continues running
๐ Key Takeaway
Memory = Hard limit โ Crash
CPU = Soft limit โ Throttle
โ๏ธ Best Practices
Always define proper requests & limits to avoid unexpected failures in production. Monitor your resource usage regularly and adjust limits based on actual consumption patterns.
#Kubernetes#DevOps#Cloud#Containers#SRE