With the use of initContainers we are able to initialize data for the volumes from the contents of the Docker container for kubernetes cluster. docker compose does this normally, but we had to do it explicitly for k8s manifests.
Another small detail was the hostnames i.e. mycodo_flask, mycodo_daemon, etc.
kubernetes doesn't like underscores for their DNS.. so I changed them all to mycodoflask, mycododaemon, etc.
P.S. it looks like I let some old commits slip in here. Let me know if you want me to re-clone and make a cleaner PR.
Thanks for this. I've been doing a lot of traveling for work and haven't had a chance to review it all yet. Just jumping in to mention it's on my radar!
With the use of initContainers we are able to initialize data for the volumes from the contents of the Docker container for kubernetes cluster.
docker compose
does this normally, but we had to do it explicitly for k8s manifests.Another small detail was the hostnames i.e. mycodo_flask, mycodo_daemon, etc. kubernetes doesn't like underscores for their DNS.. so I changed them all to mycodoflask, mycododaemon, etc.
P.S. it looks like I let some old commits slip in here. Let me know if you want me to re-clone and make a cleaner PR.