chore: move to 2.52, fix pending issues

Author: fernandezcuesta

docs/content/en/open_source/upgrading/2.51.md

@@ -30,16 +30,6 @@ This release introduces several important changes to the Helm chart configuratio
 > The previous volume implementation prevented mounting projected volumes (such as secret mounts with renamed key names) and per-container volume mounts (like nginx emptyDir when readOnlyRootFs is enforced).
 > The new approach resolves these limitations.
 
-#### Security context
-
-This Helm chart extends security context capabilities to all deployed pods and containers.
-You can define a default pod and container security context globally using `securityContext.podSecurityContext` and `securityContext.containerSecurityContext` keys.
-Additionally, each deployment can specify its own pod and container security contexts, which will override or merge with the global ones. 
-
-#### Fine-grained resources
-
-Now each container can specify the resource requests and limits.
-
 #### Moved values
 
 The following Helm chart values have been modified in this release:
@@ -49,8 +39,6 @@ The following Helm chart values have been modified in this release:
 - `redis.redisServer` → `redisServer` (prevents potential schema conflicts with upstream chart)
 - `redis.transportEncryption.params` → `redisParams` (prevents potential schema conflicts with upstream chart)
 - `postgresql.postgresServer` → `postgresServer` (prevents potential schema conflicts with upstream chart)
-- `securityContext.djangoSecurityContext` → deprecated in favor of container-specific security contexts (`celery.beat.containerSecurityContext`, `celery.worker.containerSecurityContext`, `django.uwsgi.containerSecurityContext` and `dbMigrationChecker.containerSecurityContext`)
-- `securityContext.nginxSecurityContext` → deprecated in favor of container-specific security contexts (`django.nginx.containerSecurityContext`)
 
 ### New features
 
@@ -67,7 +55,6 @@ The following Helm chart values have been modified in this release:
 - **Optional secret references**: Some secret references are now optional, allowing the chart to function even when certain secrets are not created.
 - **Fixed secret mounting**: Resolved issues with optional secret mounts and references.
 - **Improved code organization**: Minor Helm chart refactoring to enhance readability and maintainability.
-- **Extra anotations**: Now we can add common annotations to all resources.
 
 ## PostgreSQL Major Version Upgrade in Docker Compose
 

docs/content/en/open_source/upgrading/2.52.md

@@ -2,6 +2,34 @@
 title: 'Upgrading to DefectDojo Version 2.52.x'
 toc_hide: true
 weight: -20251006
-description: No special instructions.
+description: Helm chart changes.
 ---
-There are no special instructions for upgrading to 2.52.x. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.52.0) for the contents of the release.
+
+## Helm Chart Changes
+
+This release introduces more important changes to the Helm chart configuration:
+
+### Breaking changes
+
+#### Security context
+
+This Helm chart extends security context capabilities to all deployed pods and containers.
+You can define a default pod and container security context globally using `securityContext.podSecurityContext` and `securityContext.containerSecurityContext` keys.
+Additionally, each deployment can specify its own pod and container security contexts, which will override or merge with the global ones. 
+
+#### Fine-grained resources
+
+Now each container can specify the resource requests and limits.
+
+#### Moved values
+
+The following Helm chart values have been modified in this release:
+
+- `securityContext.djangoSecurityContext` → deprecated in favor of container-specific security contexts (`celery.beat.containerSecurityContext`, `celery.worker.containerSecurityContext`, `django.uwsgi.containerSecurityContext` and `dbMigrationChecker.containerSecurityContext`)
+- `securityContext.nginxSecurityContext` → deprecated in favor of container-specific security contexts (`django.nginx.containerSecurityContext`)
+
+### Other changes
+
+- **Extra annotations**: Now we can add common annotations to all resources.
+
+There are other instructions for upgrading to 2.52.x. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.52.0) for the contents of the release.

helm/defectdojo/values.yaml

@@ -285,7 +285,7 @@ django:
       # nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"
   nginx:
     # Container security context for the nginx containers.
-    containerSecurityContext: &nginxSecurityContext
+    containerSecurityContext:
       # nginx dockerfile sets USER=1001
       runAsUser: 1001
     # To extra environment variables to the nginx container, you can use extraEnv. For example:
@@ -313,7 +313,7 @@ django:
   strategy: {}
   tolerations: []
   uwsgi:
-    containerSecurityContext: &djangoSecurityContext
+    containerSecurityContext:
       # django dockerfile sets USER=1001
       runAsUser: 1001
     # To add (or override) extra variables which need to be pulled from another configMap, you can
@@ -491,7 +491,7 @@ cloudsql:
   # whether to use a private IP to connect to the database
   use_private_ip: false
   # Optional: security context for the CloudSQL proxy container.
-  containerSecurityContext:
+  containerSecurityContext: {}
   # Additional environment variables for the CloudSQL proxy container.
   extraEnv: []
   # Array of additional volume mount points for the CloudSQL proxy container