Kubernetes scanning resources overview
Last updated: January 29, 2024
Read time: 2 Minutes
If you deploy Burp Suite Enterprise Edition to Kubernetes, all of your scans run on a single, scalable pool of resources.
In this documentation, the term "auto-scaling" refers to both:
- Burp Suite Enterprise Edition automatically creating and deleting resources to handle scan jobs.
- The Kubernetes cluster automatically increasing and decreasing the number of nodes as demand changes.
You need to use both types of auto-scaling to obtain the full benefits of a Kubernetes deployment.
This section does not cover configuring the Kubernetes cluster to automatically scale its own computing resource. For information on how to configure compute power auto-scaling, check your cloud provider's documentation.
How does scanning work on Kubernetes?
When running on Kubernetes, Burp Suite Enterprise Edition automatically creates enough scan resources to cope with the number of concurrent scans that you need to run at any given time. These resources are scaled back down once they are no longer needed.
Auto-scaling means that the number of concurrent scans that you can run is not limited by how powerful your deployed machines are. Instead, your deployment can always run as many concurrent scans as your license covers.
Auto-scaling can also help to reduce maintenance and cloud infrastructure costs, as you do not need to maintain physical or virtual machines to run your scans and you only need to pay for the scan resources that you are using at any given time.
Kubernetes deployments support auto-scaling scanning resources only. You cannot run a fixed scanning machine setup on Kubernetes.
Configuring scanning resources
To manage scanning resources:
- From the settings menu select Scanning resources.
- Under Kubernetes scan containers, click View scans in progress.
From here, you can:
- Set a limit on the number of concurrent scans you want to run. This is separate from the number of concurrent scans that your license potentially allows.
- View any active scans.
- Suspend scanning altogether.
Next step - Support scope
Was this article helpful?
An error occurred, please try again.