Skip to content

docs: add upgrade guide for DefectDojo Pro on-premise (Helm) deployments #15189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devGregA wants to merge 2 commits into
base: bugfix
Choose a base branch
from
+31 −0
Open

docs: add upgrade guide for DefectDojo Pro on-premise (Helm) deployments #15189

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98cd9c2
docs: add upgrade guide for DefectDojo Pro on-premise (Helm) deployments
devGregA Jul 8, 2026
f606a10
Merge branch 'bugfix' into devgrega/docs-pro-onprem-upgrading
Maffooch Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions docs/content/get_started/pro/onprem/upgrading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
title: "Upgrading DefectDojo Pro (On-Premise)"
description: "Supported upgrade procedure for self-hosted DefectDojo Pro deployments using the Helm chart"
draft: false
weight: 5
audience: pro
---

This page describes the supported upgrade procedure for self-hosted DefectDojo Pro deployments that use the DefectDojo Pro Helm chart.

## Upgrade everything as one unit

Each DefectDojo Pro release consists of a Helm chart version, container image versions, and the Pro settings files. These are built and tested together and must be upgraded together as one unit.

Upgrading only the image tags is not supported and will break your deployment.

## Settings files and upgrades

DefectDojo Pro ships a `pro_settings.py` file with every release, and the file changes with nearly every version. Do not carry a copy of `pro_settings.py` forward across upgrades, and do not patch an older copy by hand. The application must always run the `pro_settings.py` that matches its version.

Put your own customizations in `local_settings.py`, never in `pro_settings.py`. Your `local_settings.py` is preserved across upgrades.

The Helm chart ships and mounts the matching `pro_settings.py` and your `local_settings.py` automatically. When you upgrade using the chart, there is nothing to copy or migrate by hand.

## Supported upgrade procedure

1. Review the release notes for every version between your current version and your target version, not just the target itself. See the [DefectDojo Pro Changelog](/releases/pro/changelog/) and the version-specific [upgrade notes](/releases/os_upgrading/upgrading_guide/).
2. Back up your database.
3. Upgrade to the Helm chart release that matches your target application version, reusing your existing values files. Do not change image tags independently of the chart version.

If you have questions about upgrading your on-premise deployment, contact [support@defectdojo.com](mailto:support@defectdojo.com).
Loading