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

Como é verificado

Método de auditoria: Comando shell

out=$(kubectl get pods -A -o go-template='{{range .items}}{{.metadata.namespace}} {{.metadata.name}} {{.spec.hostIPC}}{{"\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

Saída esperada

compliant

Como é corrigido

Método de correção: Orientação ou patch de infraestrutura

onfigure Pod Security Admission on workload namespaces so pods that request spec.hostIPC: true are denied at admission time. For this control, the baseline and restricted Pod Security Standards disallow hostIPC, while restricted is typically the stronger choice for user workloads. For remediation, use enforce because only enforce rejects violating pods. warn and audit can help during rollout, but they do not block admission. Label each workload namespace to enforce restricted. kubectl label ns NAMESPACE pod-security.kubernetes.io/enforce=restricted --overwrite Add warn and audit during transition if you want visibility into violations before or alongside enforcement.

Verificar este host

Execute isto em uma máquina que você tenha permissão para auditar. A varredura é somente leitura.

tmaegis scan --target oke