Skip to main content

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

Low

Address

Security

Compliance Standards

  • Cloudanix Best Practice

Triage and Remediation

Remediation

Manual Steps

  1. Identify tenant namespaces (run on any machine with kubectl access):
  2. 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 the hard values to match your tenant’s agreed limits.
  3. Apply the ResourceQuota for that tenant namespace (run on any machine with kubectl access):
  4. Repeat steps 2–3 for each remaining tenant namespace, changing the name, namespace, and quota values as appropriate.
  5. (Optional) Review existing quotas in tenant namespaces to ensure they match expectations (run on any machine with kubectl access):
  6. Verify compliance (run on any machine with kubectl access):
    Confirm that all tenant namespaces now show is_compliant=true.
Create a ResourceQuota manifest per tenant namespace. Example for a tenant namespace tenant-a:
Apply it:
Repeat with adjusted names/values for each tenant namespace.Verification (adapted from the audit):