I thought this one was already merged, I think I confused it with the one about our Drone setup for 5apps
Fixed by adding this to the session section of the app.ini:
I have switched over to ship the custom files as a Docker image, that is based on the busybox image (see e0741b4 for details). The files are copied to the persistent volume in the init container. This is much better than what I had come up with previously and is running on GKE
I don’t think that’s the case. This seems to be exactly what init containers are for, as you suggested in the beginning:
Then why does the title say “Add a script to copy the content of the custom folder to a running pod”? Shouldn’t it say “copy the custom folder to the persistent volume” in that case?
What’s wrong with simply deploying them to a PV and mounting that as /custom? I thought that was the intial approach with the init container (which would also mount the PV and copy the files oves).
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