Done in eba722992f. I created the labels as ConfigMaps and copied them to the persistent data volume as part of the init container.
This is still the old commit because we're commenting on it, new content is:
My plan was to upload them to the persistent volume, or create a small Docker container that contains these files, whichever makes more sense. kubectl cp can be used to copy files/directories to a container
Local building of images is really easy. Clone https://github.com/go-gitea/gitea and run make docker and you get a image tagged gitea/gitea:latest that you can then push. I'm updating the docs
I didn't realize the load balancers were so expensive. I have only read an introduction to Ingress so far (https://kubernetes.io/docs/concepts/services-networking/ingress/). It seems complex, but worth learning about.
It depends, I think sometimes we'll want to use releases, so official images, and sometimes we'll want an unreleased feature. production tag sounds good
Yes, but a copy of gitea/gitea:latest at the revision we want, instead of always keeping up with their latest. Creating our own images should be a separate issue
Until now we were deploying from https://hub.docker.com/r/5apps/gitea/tags/ (because we needed unreleased fixes to Let's Encrypt). We can now switch to the 1.7 release from the official images (https://hub.docker.com/r/gitea/gitea/tags/)
What happened to removing the obsolete env vars? I just found them in master.