Skip to main content

More Info:

Verifies the default namespace has no workloads so RBAC, quotas and NetworkPolicies can be scoped per tenant.

Risk Level

Medium

Address

Security

Compliance Standards

  • Cloudanix Best Practice

Triage and Remediation

Remediation

Manual Steps

  1. List all workloads in the default namespace (from any machine with kubectl access)
  2. Identify each controller-backed workload and its type (from any machine with kubectl access)
  3. Create appropriate target namespaces (from any machine with kubectl access)
    Replace team-a / team-b with your desired namespace names and repeat as needed:
  4. Export and re‑apply controller-based workloads into the target namespace(s) (from any machine with kubectl access)
    Example for moving a Deployment named web from default to team-a (repeat per workload, adjusting names and target namespace):
  5. Handle standalone Pods and Services in default (from any machine with kubectl access)
    For any Pods not managed by a controller, recreate them in the correct namespace (usually by adding metadata.namespace to their original manifest) and then delete from default. Example for a standalone Pod and a Service:
  6. Verification: confirm default has zero Pods (from any machine with kubectl access)