Frontend + Backend Integrated Deployment (K8s only)

[ikreymer]

In support of #19, this combines the frontend + backend running on a single domain.
The backend and frontend run on separate services and can be deployed independently, though currently with the same helm chart.
The backend is then run entirely from /api endpoint, eg. /api/docs

Contains:

• Creating custom nginx container with own Docker image, which simply contains the frontend files
• Splitting nginx container into own k8s service, which can be deployed separately (but requires image update)
• Configuring backend to serve via /api prefix
• Configuring ingress to point to backend service for /api prefix.
• Support for --set frontend_only=1 and --set backend_only=1 helm chart settings to redeploy only one or the other.

Questions/TODO:

• The frontend image packages main.js and index.html, although there's a bunch of other chunks that are build. Probably need to set up a production build of the frontend to make this more robust? @SuaYoo
• Investigate if makes sense to have separate helm chart for frontend, which doesn't need any backend config options

[SuaYoo]

Created #46 for frontend prod build settings

[SuaYoo]

#46

[SuaYoo]

Looks good, a few comments:

• Did you manually delete frontend/src/__generated__? If so, what was the reason?
• Per discord convo, frontend isn't running in local docker yet

[ikreymer]

Looks good, a few comments:

• Did you manually delete frontend/src/__generated__? If so, what was the reason?

Yes, oops, that was my mistake! I think I saw generated and thought it was something I added by accident, will revert.

• Per discord convo, frontend isn't running in local docker yet

yep, will see can fix before merging