Cis K8S V1111 1.3.2

1.3.2 Ensure that the --profiling argument is set to false (Automated)

Profile Applicability

• Level 1 - Master Node

Description

Disable profiling, if not needed.

Rationale

Profiling allows for the identification of specific performance bottlenecks. It generates a significant amount of program data that could potentially be exploited to uncover system and program details. If you are not experiencing any bottlenecks and do not need the profiler for troubleshooting purposes, it is recommended to turn it off to reduce the potential attack surface.

Impact

Profiling information would not be available.

Audit

Run the following command on the Control Plane node:

ps -ef | grep kube-controller-manager

Verify that the --profiling argument is set to false.

Remediation

Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml on the Control Plane node and set the below parameter.

--profiling=false

Default Value

By default, profiling is enabled.

References

1. https://kubernetes.io/docs/admin/kube-controller-manager/
2. https://github.com/kubernetes/community/blob/master/contributors/devel/profiling.md

CIS Controls