A building-permits namespace must not over-request PVC storage. Which Kubernetes control caps total PVC storage requests in that namespace?
Select an answer to reveal the explanation.
Short Explanation
ResourceQuota is the namespace budget sheet—it can say “this team only gets this much claimed disk,” so PVC requests stop when the budget’s gone.
Full Explanation
A building-permits namespace that must not over-request PVC storage is capped with a ResourceQuota that limits persistentvolumeclaims and/or requests.storage in that namespace. ResourceQuota is the namespace budget sheet—it can say this team only gets this much claimed disk, so new PVC requests stop when the budget is gone.
A PodDisruptionBudget with maxUnavailable zero manages voluntary disruptions, not storage quotas. A LimitRange that only sets default CPU requests does not provide the aggregate PVC storage cap described here. A NetworkPolicy denying egress to the CSI driver is not a quota mechanism and may break provisioning side effects without expressing a storage budget.
Exam caveat: quota is checked at admission; teams see Forbidden errors when exceeding limits. LimitRanges can set per-PVC min/max storage but ResourceQuota is the aggregate namespace control called out in the question.
Operational check: apply a ResourceQuota with storage and PVC count limits, attempt an oversized PVC in the permits namespace, confirm rejection, and show teams their remaining budget via kubectl describe quota. Keep civic change tickets precise: record object names, namespaces, and before/after observations so the next on-call engineer can replay the fix without guesswork.