Use the CI-published :latest tag with pullPolicy Always, since the chart
previously defaulted to appVersion 0.1.0, which is not published as an image.
Add ingress annotations with a cert-manager ClusterIssuer so the TLS secret is
issued instead of having to exist beforehand.
Extend release.sh --deploy to create the registry image pull secret from the
local Docker config and pass it to the release, and document both the scripted
and manual deployment paths.
A multi-stage kaniko build replaces / with the last stage's root filesystem,
which deletes $HOME/.docker/config.json. Kaniko then resolves credentials at
push time without them, asks the registry for an anonymous token and Gitea
rejects the upload with 401 reqPackageAccess.
Keep the Docker credential store in /kaniko/.docker for the whole image job via
DOCKER_CONFIG and let docker login write there directly. Restore the image job
and document that CI publishes images again.
The Gitea registry rejects kaniko pushes from job containers with
401 reqPackageAccess even though the same credentials work from a normal
machine, so the image job could never go green.
Drop the image job; CI now only runs unit tests, the smoke test and the
Helm chart lint. Add scripts/release.sh, which builds and pushes the
image from a trusted machine and can optionally apply the users secret
and run helm upgrade.