feat(deployment)!: move image to deployment.gitea.image

The `image` values only ever configured the Gitea container itself — registry, repository, tag, digest,
pull policy and the rootless variant are all consumed by the `gitea` container and its init containers.
Keeping them at the top level suggested a chart-wide scope that never existed and separated them from the
other container-scoped settings that already live under `deployment.gitea` (`env`, `resources`).
Moving the block makes the container configuration self-contained and continues the consolidation of all
pod- and Deployment-scoped values under the `deployment` dict.

`imagePullSecrets` intentionally stays top-level, because it is a pod-level setting that also applies to
`extraContainers` and is paired with `global.imagePullSecrets`.

BREAKING CHANGE: `image` no longer exists. Use `deployment.gitea.image` instead. Values still set under
`image` are silently ignored, which would drop a pinned `tag` or `digest` and roll out the chart default
(`appVersion`) instead — review your values before upgrading.

Co-authored-by: Copilot <copilot@github.com>
This commit is contained in:
2026-09-04 13:07:47 +02:00
co-authored by Copilot
parent f385d22b56
commit 3c9fc19829
10 changed files with 116 additions and 109 deletions
@@ -7,7 +7,7 @@ templates:
tests:
- it: runs gpg in batch mode
set:
image.rootless: false
deployment.gitea.image.rootless: false
secrets.gpg.enabled: true
secrets.gpg.new.privateKey: |-
-----BEGIN PGP PRIVATE KEY BLOCK-----
@@ -23,7 +23,7 @@ tests:
gpg --batch --import "$TMP_RAW_GPG_KEY"
- it: skips gpg script block for disabled signing
set:
image.rootless: false
deployment.gitea.image.rootless: false
asserts:
- equal:
path: stringData["init_directory_structure.sh"]
@@ -42,7 +42,7 @@ tests:
chmod -v ug+rwx "${GITEA_TEMP}"
- it: adds gpg script block for enabled signing
set:
image.rootless: false
deployment.gitea.image.rootless: false
secrets.gpg.enabled: true
secrets.gpg.new.privateKey: |-
-----BEGIN PGP PRIVATE KEY BLOCK-----