I checked again, there aren't any tk-vagrant-main-ubuntu persistent disks right now
I need to figure out why it's creating persistent disks. The integrations tests are using Test Kitchen with the gce driver, because the Vagrant driver didn't work inside of Kubernetes
I don't know what the 100GB disks are, they're not any of the persistent disks in the GKE console
The tk disks are from running the integrations tests on the chef repo using GKE
There is no way to create a configmap from a directory containing subdirectories and files (you need to pass every file), so I need to rethink the process if we want to add more custom files easily. I had also misunderstood ConfigMaps, the GKE docs are more explicit about it being for key-value pairs, so it would not work for every file (https://cloud.google.com/kubernetes-engine/docs/concepts/configmap). Copying a folder recursively to a location on a pod seems possible with kubectl cp, I'm trying that out. Creating a Docker image just for copying these custom files seems overkill
Here's the Docker docs where they say /data/gitea is the folder for customization when using Docker: https://docs.gitea.io/en-us/install-with-docker/#customization
I don’t know what that means. The files live in an actual /custom folder with my local Gitea that I’m developing them in. The docs call that folder /custom. If you put them in the normal data folder, then almost certainly they will overwrite actual Gitea files, instead of adding custom ones in the custom folder.
I think it's not a big change from this PR to achieve that (create ConfigMaps for the entire folder instead of just options/label, copy the mounted files to /data/gitea/, this is what the Gitea docs call /custom). The secrets (app.ini and the dummy TLS cert) will have to be moved respectively to custom/conf and custom/https
Done in eba722992f. I created the labels as ConfigMaps and copied them to the persistent data volume as part of the init container.