Back to Practice
Lab

Namespace Quotas and Limits

Stop one team from starving the cluster: cap a namespace's total requests, limits, and object counts with a ResourceQuota, and hand every container a sensible default with a LimitRange.

Your mission

Two admission controls keep a shared cluster fair:

  • a ResourceQuota caps a namespace's totals — how much CPU/memory it may request and limit in aggregate, and how many objects it may create.
  • a LimitRange sets per-container defaults and bounds, so a Pod that names no requests still gets sensible ones (which a ResourceQuota then requires).

You'll apply both to the team-a namespace.

kubectl config set-context --current --namespace=team-a

Skills you'll put into practice

adminquotascka

Make it your own.

Use this topic as a starting point for a fresh custom scenario.

Create a variation