Vertex

Resource limits and troubleshooting

Requests drive scheduling, limits drive eviction. CrashLoopBackOff and OOMKilled are usually a limits conversation, not a code one.

Lesson 4.35m 8sAdvanced3.7k students

Chapters

5:08
  1. 0:00OOMKilled: Understanding Memory Limit Issues
  2. 0:26What is OOMKilled?
  3. 1:03Common Causes
  4. 1:37Detecting OOMKilled
  5. 2:08Memory: Requests vs Limits
  6. 2:45Setting Memory Limits
  7. 3:21Troubleshooting Steps
  8. 4:03Prevention Best Practices
  9. 4:52Outro

What this lesson covers

  • Set requests and limits that reflect real usage
  • Diagnose CrashLoopBackOff and OOMKilled pods
  • Debug a pod with logs, describe, and exec

This lesson sits in Operating a Cluster, part of DevOps with Docker and Kubernetes. It assumes what came before it and leads directly into the next lesson in the module.

In this lesson you will

  • Set requests and limits that reflect real usage
  • Diagnose CrashLoopBackOff and OOMKilled pods
  • Debug a pod with logs, describe, and exec

Resources

Previous lessonAutoscaling workloads4.2 · 28m 5s