feat(ci): kubernetes deployment

[themightychris]

Don't have this working yet, running into weird auth problems with my local kind cluster pulling from ghcr.io even though I had a regcred secret in place that looked good

This might be enough for a working deploy after that, but I have no idea if my use of hostAliases will make the app and db hostnames hardcoded into the frontend nginx config and backend will work. Ultimately we want the backend connecting to a database provided through env, and to probably let k8s' ingress handle mounting /api

TODO:

• Remove line from Dockerfile
• Mount / with docker-compose
• Create ingress path for container on /api
• Django App: Receive DB Hostname and Creds through ENV

[themightychris]

ah ha, I've never used ghcr.io before, you have to explicitly switch a package to public after you publish it

edit: oh wow it works! in my local kind cluster at least

[themightychris]

we should probably remove the line i added to dockerfile to copy nginx config in. If the container build without that provides for serving the static content out of /, then that can be something we just mount with docker-compose and the k8s ingress can handle plugging the api into the /api path on top of it, and then that gets rid of the need for the app hostAlias

the next piece then would be getting the django app to take its DB hostname and auth through env vars so we can get rid of the other hostAlias and just have k8s and docker-compose both pass down appropriate hostnames

[MooseQuest]

Approving and Merging