Helm Chart Requirements

The Detectify Internal Scanning engine can be deployed to a Kubernetes cluster using Helm.

Requirements for deploying the Internal Scanning Agent on Kubernetes are documented below.

Software Tools

Install these tools on your workstation:

# Make sure they're installed correctly
kubectl version
helm version

Kubernetes Cluster

The Internal Scanner runs on Kubernetes. Your cluster needs:

Persistent Volumes

Unless you intend to use an externally managed Redis, the cluster needs to support PersistentVolumeClaim to provide Redis with persistent data storage.

kubectl get storageclass
# NAME            PROVISIONER                 RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
# ebs-gp3         ebs.csi.eks.amazonaws.com   Delete          WaitForFirstConsumer   true                   21h
# gp2 (default)   kubernetes.io/aws-ebs       Delete          WaitForFirstConsumer   false                  21h

For Scanner API

If you need to interact with Internal Scanning via the REST API (i.e. not via the Detectify UI) the cluster also needs to support:

• Ingress (e.g. nginx-ingress)
• Certificate issuing (e.g. cert-manager)
• DNS management (e.g. external-dns)

Network

Outbound Access

The scanner needs outbound HTTPS access to:

Detectify Credentials

You need credentials and a license key.

Don’t have credentials? Contact your Detectify account team or reach out to us  to enable Internal Scanning.

Next Steps

• Deploy on Kubernetes — Helm chart for any cluster