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
-
List all tenant namespaces (excluding system namespaces). Run on any machine with kubectl access:
-
For each tenant namespace (replace TENANT_NAMESPACE with the actual name), create a baseline ResourceQuota manifest file locally, for example
rq-tenant-TENANT_NAMESPACE.yaml:Adjust the values to match your tenant sizing and capacity planning. -
Apply the ResourceQuota for each tenant namespace. Run on any machine with kubectl access:
-
(Optional) Review the applied ResourceQuota and confirm it matches expectations. Run on any machine with kubectl access:
-
If you already use labels to identify tenant namespaces (for example
tenant=true), you can target only those namespaces. Run on any machine with kubectl access:Whererq-tenant-template.yamlis the manifest from step 2 withTENANT_NAMESPACEas a placeholder. -
Verify that every tenant namespace now has at least one ResourceQuota. Run on any machine with kubectl access:
Confirm that
is_compliant=truefor all tenant namespaces.
Using kubectl
Using kubectl
Automation
Automation

