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 that has no ResourceQuota, create a baseline ResourceQuota manifest file (run on any machine with kubectl access). Example for namespace
tenant-a:Adjust thehardvalues to match your tenant’s agreed limits. -
Apply the ResourceQuota for that tenant namespace (run on any machine with kubectl access):
-
Repeat steps 2–3 for each remaining tenant namespace, changing the
name,namespace, and quota values as appropriate. -
(Optional) Review existing quotas in tenant namespaces to ensure they match expectations (run on any machine with kubectl access):
-
Verify compliance (run on any machine with kubectl access):
Confirm that all tenant namespaces now show
is_compliant=true.
Using kubectl
Using kubectl
tenant-a:Automation
Automation

