Creating another Pod in the permits namespace returns Forbidden with a message that a ResourceQuota is exceeded for pods count. What does that indicate?
Select an answer to reveal the explanation.
Short Explanation
ResourceQuota is the apartment building’s unit cap — once the building is full, new leases are refused. Forbidden plus quota exceeded means the namespace budget, not a NetworkPolicy or disk-pressure riddle.
Full Explanation
Creating another Pod in the permits namespace returns Forbidden with a message that a ResourceQuota is exceeded for pods count. That indicates a namespace ResourceQuota has capped how many Pods may exist, so admission denies the create before persistence. Object-count quotas are a common municipal guardrail against runaway replica experiments consuming Pod capacity, controller load, and cluster IP space.
Claiming the node's disk pressure always surfaces as a ResourceQuota Forbidden on Pod creates fails—disk pressure presents via node conditions and eviction, not quota admission messages. Claiming missing LimitRange defaults are reported as quota exceeded confuses LimitRange defaulting with ResourceQuota hard limits. Claiming NetworkPolicy ingress rules block kubectl create by returning quota errors fails because NetworkPolicies govern Pod traffic, not API admission for object counts.
Exam caveat: remaining CPU or memory quota does not imply remaining pods-count quota; each hard resource name is independent. Operational check: kubectl describe resourcequota -n permits, reduce Pod counts or request a platform increase to the pods hard limit, retry creation, and confirm admission succeeds without Forbidden.