Ensure the --profiling argument is set to False

Error: The --profiling argument is not set to False

Bridgecrew Policy ID: BC_K8S_87
Checkov Check ID: CKV_K8S_114
Severity: LOW

The --profiling argument is not set to False

Description

Disable 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.

Fix - Buildtime

Kubernetes

  • Kind: Pod
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    component: kube-scheduler
    tier: control-plane
  name: kube-scheduler
  namespace: kube-system
spec:
  containers:
  - command:
+   - kube-scheduler
+   - --profiling=false
    image: gcr.io/google_containers/kube-scheduler-amd64:v1.6.0

Did this page help you?