Skip to main content

More Info:

Turn on Role Based Access Control.

Risk Level

High

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, back up the existing kube-apiserver static pod manifest:
  2. On every control plane node, open the manifest for editing:
    Locate the - --authorization-mode=... line under spec.containers[].command. If it does not exist, add it; if it exists, modify it so that it includes RBAC, for example:
    Save and exit. Editing this file will cause the kube-apiserver static pod to restart automatically.
  3. On every control plane node where you changed the file, confirm the kube-apiserver pod has restarted and is running:
  4. On every control plane node, verify the kube-apiserver process now includes RBAC in the --authorization-mode argument:
    Confirm the output shows --authorization-mode with a value that includes RBAC (for example, --authorization-mode=Node,RBAC).
kubectl cannot modify the kube-apiserver static pod manifest or its process flags. This finding must be remediated directly on each control plane node by editing /etc/kubernetes/manifests/kube-apiserver.yaml; see the Manual Steps section for exact instructions.

Additional Reading: