Red Hat OpenShift
TMA-OPENSHIFT-5.7.1
Create administrative boundaries between resources using namespaces
LowLevel 1Manual reviewopenshift
Description
Use namespaces to isolate your Kubernetes objects. The benchmark marks this recommendation Manual.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
OpenShift Projects wrap Kubernetes namespaces and are used by default in OpenShift 4. Run the following command to obtain a list of all non-default OpenShift and Kubernetes namespaces in the cluster. oc get namespaces -o json | jq '.items[] | select(.metadata.name|test("(?!default|kube-.|openshift.)^.*")) | .metadata.name' Ensure that these namespaces are the ones you need and are adequately administered as per your requirements.
How it is fixed
Fix method: Guidance or infrastructure patch
Follow the documentation and create namespaces for objects in your deployment as you need them.
Properties
- Operating systems
- Any
- Tags
- openshiftpolicies
- Reference
- CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.7.1 Create administrative boundaries between resources using namespaces