feat!: remove the deprecated extraVolumeMounts value

`extraVolumeMounts` was deprecated in 6.0.0 in favour of separate mounts for the init phase and the runtime container,
but it was never removed. It had turned into a trap: both helpers treated it as a fallback that silently disappeared as
soon as `extraInitVolumeMounts` respectively `deployment.gitea.volumeMounts` contained a single entry, so adding one
new mount could unmount everything configured through the old value. The documented successor
`extraContainerVolumeMounts` had meanwhile been removed itself, which left the deprecation note pointing at a value
that already fails the deprecation check.

Removing it makes the mount configuration explicit: `extraInitVolumeMounts` for the init containers,
`deployment.gitea.volumeMounts` for the Gitea container, and both when a volume is needed in both places.

The GPG init container used `extraVolumeMounts` directly instead of the shared helper and therefore ignored
`extraInitVolumeMounts`, unlike the three other init containers. It now uses `gitea.init-additional-mounts` as well.

Co-authored-by: Copilot <copilot@github.com>

This commit is contained in:

volker.raschek

2026-10-03 19:14:20 +02:00

co-authored by

Copilot

parent ccd470557f

commit c96e5d4132

6 changed files with 23 additions and 17 deletions

									
										templates/_initContainers.tpl
									
		+1
		-3
	
												View File
												
				@@ -174,9 +174,7 @@

				    - name: gpg-private-key

				      mountPath: /raw

				      readOnly: true

				    {{- if .Values.extraVolumeMounts }}

				    {{- toYaml .Values.extraVolumeMounts | nindent 4 }}

				    {{- end }}

				    {{- include "gitea.init-additional-mounts" . | nindent 4 }}

				    {{- with $config.volumeMounts }}

				    {{- toYaml . | nindent 4 }}

				    {{- end }}