Add CI job to build and publish docker image and helm chart#7
Add CI job to build and publish docker image and helm chart#7douglaswinter merged 5 commits intomainfrom
Conversation
This chart handles deployment, services, ingress, etc so that app charts depending on this can simply declare which UI image to run and what ser- vices to talk to.
Triggered on release (or manually) with tags following appname@semver. appname must match /apps/appname. Expects to find /apps/appname/helm.
douglaswinter
requested review from
VictoriaBeilsten-Edmands and
noemifrisina
noemifrisina
left a comment
noemifrisina
left a comment
There was a problem hiding this comment.
Don't really know enough about helm for a proper review, but this looks good to me - makes it easier to see all the moving parts for someone who doesn't know too much about helm charts.
One question - do we have a way to automatically generate the single application charts for each app yet, or should we create them from scratch? Whichever is the case - may be worth mentioning...
Only other comment I have is that finding the information by opening different readmes could get annoying in the long run - I think it might be worth it to set up some docs and move everything in there (in a separate PR, happy to give it a shot)
Thanks! Issue created to create a turbo generator to bootstrap new app, which will include that Helm chart. And yes, we need a docs project |
2 participants
Triggered by release (or workflow dispatch) with tagging convention appName@semver, where appName is expected to match an app in /apps.
Also expects to find /apps/appName/helm. Base Helm chart provided that handles the heavy-lifting of deploying an authenticated web app, with the app chart simply needing to specify which image to run and what backend services to use.