More Info:
Advisory: create a ResourceQuota per tenant namespace to bound aggregate CPU, memory and object counts, preventing one tenant from starving others.Risk Level
LowAddress
SecurityCompliance Standards
- Cloudanix Best Practice
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
Identify tenant namespaces (run on any machine with kubectl access):
-
For each tenant namespace (replace TENANT_NAMESPACE with the real name), create a ResourceQuota limiting aggregate CPU, memory, and object counts (run on any machine with kubectl access):
Adjust the
hardvalues to match your tenant’s expected usage and SLOs before running. -
If different tenants need different limits, create separate manifests per namespace with tuned values (run on any machine with kubectl access):
-
(Optional) Confirm per-namespace enforcement details for a specific tenant (run on any machine with kubectl access):
-
Verification: confirm that every tenant namespace now has at least one ResourceQuota (run on any machine with kubectl access):
Ensure all tenant namespaces show
is_compliant=true.
Using kubectl
Using kubectl
Automation
Automation

