It was found that the argument --profiling in the Scheduler pod specification file is not set to False. Profiling is used to identify performence bottlenecks. When enabled, the feature can be exploited by a malicious actor to uncover system and program details.
Recommended Mitigation
It is recommended to edit the Scheduler pod specification file on the master node and set the parameter ""False"" to the --profiling argument.
Best practices
