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 (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 hard values to match your tenant’s expected usage and SLOs before running.
  3. If different tenants need different limits, create separate manifests per namespace with tuned values (run on any machine with kubectl access):
  4. (Optional) Confirm per-namespace enforcement details for a specific tenant (run on any machine with kubectl access):
  5. 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.