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):
  1. For each tenant namespace without a ResourceQuota, create a baseline manifest file locally (edit the namespace and limits/requests as appropriate):
  1. Apply the ResourceQuota for that tenant namespace (run once per namespace after editing the manifest):
  1. (Optional) Review the effective quotas in each tenant namespace to ensure they reflect your capacity and fairness goals:
  1. Repeat steps 2–4 for every tenant namespace that needs its own tailored resource bounds.
  2. Verification (run on any machine with kubectl access):