Unlock enhanced API scanning with Burp Suite Enterprise Edition  –  Learn more

Enterprise Edition

System requirements for a Kubernetes instance

  • Last updated: April 18, 2024

  • Read time: 2 Minutes

You can deploy Burp Suite Enterprise Edition to Kubernetes. We provide a Helm chart with the correct field values to meet the minimum system requirements.

Note

We recommend that you only attempt to deploy and manage Burp Suite Enterprise Edition in a Kubernetes environment if you have previous Kubernetes experience.

To deploy Burp Suite Enterprise Edition to Kubernetes, you need a cluster that meets the following requirements:

  • An ingress solution, for example a load balancer or an ingress controller.
  • A PersistentVolumeClaim that is created in the namespace to which Burp Suite Enterprise Edition is going to be deployed. The access mode is ReadWriteMany.
  • A PersistentVolume bound to the PersistentVolumeClaim. They must be able to be simultaneously accessed by all nodes that are available to the namespace to which Burp Suite Enterprise Edition is going to be deployed. The access mode is ReadWriteMany.
  • (Optional) To enable cluster node autoscaling, the cluster-autoscaler must be installed and enabled.
  • An external database that meets our system requirements.

Burp Suite Enterprise Edition can run on an x86-based cluster. There may be additional infrastructure configuration required depending on your Kubernetes environment. Please refer to our Kubernetes support scope and setup guide.

Warning

For security reasons, make sure you set your cluster up in a way that prevents your scanning resources from accessing any network systems or functionality that you don't intend to scan.

Container system requirements

We specify the hardware resources for the containers in our Helm chart values file.

Note

Make sure your cluster node type is set appropriately for your environment.

CentOS/RHEL v7.x operating systems are not supported for the cluster worker node.

Minimum requirements for general container limits

These are the minimum and maximum limits for all your containers in the namespace.

Field

Value

maxCpuPerContainer

4000m

minCpuPerContainer

100m

maxMemoryPerContainer

8Gi

minMemoryPerContainer

128Mi

Minimum requirements for a web server container

Field

Value

webServerContainerCpu

1400m

webServerContainerMemory

2Gi

Minimum requirements for an Enterprise server container

Field

Value

enterpriseServerContainerCpu

1400m

enterpriseServerContainerMemory

2Gi

Minimum requirements for a scan container

Field

Value

scanContainerCpu

4000m

scanContainerMemory

8Gi

If you need help with the system requirements, please email our support team.

Next step - System requirements for your external database

Was this article helpful?