feat(deployment)!: move `topologySpreadConstraints` to `deployment.topologySpreadConstraints`

The top-level `topologySpreadConstraints` value only ever configured the pod spec of the Gitea Deployment, yet
it lived next to chart-wide settings. This made it hard to tell which values influence the Deployment and which
apply to the chart as a whole. Moving it into the `deployment` dict continues the consolidation already done for
`affinity`, `dnsConfig`, `nodeSelector`, `priorityClassName` and `resources`, so all pod scheduling settings are
now grouped in one predictable place.

A deprecation check fails the release when the removed top-level value is still set. Silently ignoring it would
be particularly harmful here: the constraints would be dropped without any warning and all replicas could end up
scheduled on a single node or zone, defeating the availability guarantees the user configured.

BREAKING CHANGE: `topologySpreadConstraints` no longer exists. Use `deployment.topologySpreadConstraints`
instead. Installations that still set `topologySpreadConstraints` will fail unless `checkDeprecation` is set to
`false`.

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

This commit is contained in:

volker.raschek

2026-09-04 11:52:17 +02:00

co-authored by

Copilot

parent 20de800294

commit 9e12eeccab

6 changed files with 50 additions and 7 deletions

									
										templates/gitea/deployment.yaml
									
		+1
		-1
	
												View File
												
				@@ -433,7 +433,7 @@ spec:

				      affinity:

				        {{- toYaml . | nindent 8 }}

				    {{- end }}

				    {{- with .Values.topologySpreadConstraints }}

				    {{- with .Values.deployment.topologySpreadConstraints }}

				      topologySpreadConstraints:

				        {{- toYaml . | nindent 8 }}

				    {{- end }}

feat(deployment)!: move topologySpreadConstraints to deployment.topologySpreadConstraints

feat(deployment)!: move `topologySpreadConstraints` to `deployment.topologySpreadConstraints`