InformationDisable profiling, if not needed.
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.
SolutionEdit the `/etc/kubernetes/apiserver` file on the master node and set the `KUBE_API_ARGS` parameter to `'--profiling=false'`: `KUBE_API_ARGS='--profiling=false'`
Based on your system, restart the `kube-apiserver` service. For example: `systemctl restart kube-apiserver.service`
Profiling information would not be available.