Version: Current


kube-hunter hunts for security weaknesses in Kubernetes clusters. The tool was developed to increase awareness and visibility for security issues in Kubernetes environments. You should NOT run kube-hunter on a Kubernetes cluster that you don't own!

To learn more about the kube-hunter scanner itself visit kube-hunter GitHub or kube-hunter Website.


The kube-hunter ScanType can be deployed via helm:

helm upgrade --install kube-hunter secureCodeBox/kube-hunter

Scanner Configuration

The following security scan configuration example are based on the kube-hunter Documentation, please take a look at the original documentation for more configuration examples.

  • To specify remote machines for hunting, select option 1 or use the --remote option. Example: kube-hunter --remote
  • To specify interface scanning, you can use the --interface option (this will scan all of the machine's network interfaces). Example: kube-hunter --interface
  • To specify a specific CIDR to scan, use the --cidr option. Example: kube-hunter --cidr

Chart Configuration

image.repositorystring""Container Image to run the scan
image.tagstringnildefaults to the charts version
parserImage.repositorystring""Parser image repository
parserImage.tagstringdefaults to the charts versionParser image tag
scannerJob.envlist[]Optional environment variables mapped into each scanJob (see:
scannerJob.extraContainerslist[]Optional additional Containers started with each scanJob (see:
scannerJob.extraVolumeMountslist[]Optional VolumeMounts mapped into each scanJob (see:
scannerJob.extraVolumeslist[]Optional Volumes mapped into each scanJob (see:
scannerJob.resourcesobject{}CPU/memory resource requests/limits (see:,
scannerJob.securityContextobject{}Optional securityContext set on scanner container (see:
scannerJob.ttlSecondsAfterFinishedstringnilDefines how long the scanner job after finishing will be available (see:



apiVersion: ""
kind: Scan
name: "kube-hunter-in-cluster"
scanType: "kube-hunter"
- "--pod"