All 15 Docker & Deployment questions
More in Docker & Deployment
How does Docker Compose simplify local development for a Node.js application that depends on a database and a cache? What is a .env file, and how does it interact with a Dockerized Node.js application's configuration? What is the purpose of a HEALTHCHECK instruction in a Dockerfile for a Node.js application? How do Kubernetes ConfigMaps and Secrets differ, and how are they typically consumed by a Node.js pod? How do you properly handle process signals (SIGTERM) inside a containerized Node.js application to support graceful shutdown? Why should a Node.js Docker container generally run as a non-root user, and how do you configure this in a Dockerfile? How would you optimize Docker layer caching in a Node.js Dockerfile to speed up repeated builds during development? What is the difference between deploying a Node.js application to a Platform-as-a-Service (like Heroku or Render) versus a self-managed container orchestrator (like Kubernetes)? What is a Kubernetes Deployment's rolling update strategy, and how does it apply to updating a running Node.js application? How do you handle running database migrations as part of a Kubernetes-based Node.js deployment pipeline?
Advertisement
Back to results for “Debugging”
Node.js › Docker & Deployment

What is the purpose of setting explicit CPU and memory resource requests and limits for a Node.js container in Kubernetes?

Intermediate

Answer

A resource request tells Kubernetes the minimum CPU/memory a container needs, used for scheduling decisions (placing the pod only on a node with enough available capacity); a limit caps the maximum a container can consume, with Kubernetes throttling CPU usage above the limit or killing (OOMKilling) the container if it exceeds its memory limit -- setting these appropriately prevents one misbehaving pod from starving others on the same node, and prevents a memory leak from silently degrading the entire node.
resources:
  requests:
    memory: '256Mi'
    cpu: '250m'
  limits:
    memory: '512Mi'
    cpu: '500m'
Real-world example A team without resource limits on their Node.js pods experienced a memory leak in one service gradually consuming all available memory on a shared node, starving unrelated pods; adding a memory limit ensures that specific pod gets OOMKilled and restarted long before it can impact its neighbors.

Common follow-ups: How do you determine appropriate request and limit values without either wasting capacity or risking throttling/OOMKills under normal load?;What's the difference in behavior between exceeding a CPU limit versus exceeding a memory limit?

Performance Optimization & Profiling;Debugging & Diagnostics
All 15 Docker & Deployment questions