Updating Burp Suite Enterprise Edition on Kubernetes
Last updated: January 29, 2024
Read time: 2 Minutes
Kubernetes deployments of Burp Suite Enterprise Edition do not update automatically. However, because all data is held within the database rather than the app itself, you can easily update the installation without affecting any of your configuration settings.
Preparing to update
Before you update Burp Suite Enterprise Edition, you should disable scanning. Any queued scans (that is, scans that have been created by the system but not yet started) will fail if they attempt to run during the update process.
To disable scanning, open the Scan resources settings page and set the Enable scanning toggle to off. This prevents Burp Suite Enterprise Edition from creating any new scans.
Disabling scanning does not affect any scans that are currently in progress. You can safely let these scans run while updating, as any scans that have already started are not affected by the update process.
Running the update command
To update a Kubernetes installation of Burp Suite Enterprise Edition:
- Download the latest version of the Helm chart from the Releases page or the Helm chart GitHub repository.
- Unpack the new chart into a directory of your choice. Note that you will need the name of this directory when running commands against the chart.
- Run the update command:
helm upgrade -n <namespace> <deployment name> <name of directory containing the chart>
For example, to use a chart located in
enterprise-helm-folder to update a deployment of Burp Suite Enterprise Edition called
bsee-deployment with a namespace of
bsee-namespace, you would run:
helm upgrade -n bsee-namespace bsee-deployment enterprise-helm-folder
After you have run the update command, the application updates immediately. Note that there may be a few seconds of downtime during the process.
Once the system has resumed, you can re-enable scanning by opening the Scan resources settings page and setting the Enable scanning toggle to off.
Although Burp Suite Enterprise Edition does not update automatically, the Scanner component can update automatically if configured to do so. For more information on configuring Scanner updates, see the Managing Updates page.
Was this article helpful?
An error occurred, please try again.