Minimize the admission of containers wishing to share the host network namespace

Cómo se verifica

Método de auditoría: Comando de shell

out=$(kubectl get pods -A -o go-template='{{range .items}}{{.metadata.namespace}} {{.metadata.name}} {{.spec.hostNetwork}}{{"\n"}}{{end}}') || exit 1
bad=$(printf '%s\n' "$out" | awk -v ex='^(kube-system|kube-public|kube-node-lease)$' 'NF && $1 !~ ex && ($3=="true")')
if [ -z "$bad" ]; then echo compliant; else printf '%s\n' "$bad" | head -n 25; fi

Salida esperada

compliant

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

Configure Pod Security Admission on workload namespaces so pods that request spec.hostNetwork: true are denied at admission time. Use enforce on workload namespaces with restricted, or at minimum baseline, and reserve any exceptions for narrowly approved platform workloads. After updating namespace enforcement, remove hostNetwork: true from affected manifests and redeploy those workloads so new pods are evaluated under the enforced policy. For this control, the baseline and restricted Pod Security Standards disallow hostNetwork, while restricted is typically the stronger choice for user workloads. Label each workload namespace to enforce restricted. kubectl label ns NAMESPACE pod-security.kubernetes.io/enforce=restricted --overwrite Add warn and audit during rollout if you want visibility into violations, but do not rely on them for remediation because they do not block pod creation.

Verificar este host

Ejecute esto en un equipo que tenga permiso para auditar. El escaneo es de solo lectura.

tmaegis scan --target oke