-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for deploying via Helm chart #1602
Comments
We're also using helm for a few of our internal deploys...I can see about opening some of that up and pushing it to github. I also recently read the following post: https://helm.sh/blog/helm-turns-five/ and so I think the timing is good.
|
That would be great, thank you! +1 for helm-chart-releaser & https://github.com/norwoodj/helm-docs Let me know if I can help setting it up or give feedback at some point. |
For what is worth we have a bare bones FHIR chart, with limited configurability to suit some demos we have been doing. It's available in the alvearie health-patterns repository in case someone might want to use it in the mean time, while the official chart from the FHIR team is published. We are planning on using this official chart too once it's available. |
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Extracting a standalone helm chart from the one we use within our internal deploy pipeline proved a bit more difficult than I was expecting. I created a draft pull request #1848 with a "clean base" but left quite a few TODOs in the description. Will try getting back to this one when I have a chance. |
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
The initial version of this chart is now committed to https://github.com/Alvearie/alvearie-helm/tree/main/ibm-fhir-server. |
Is your feature request related to a problem? Please describe.
The server is currently not available as a Helm chart, making installation on Kubernetes less convenient.
Describe the solution you'd like
Provide a Helm chart the make it easier to install the application in Kubernetes.
Describe alternatives you've considered
Additional context
I could definitely work on this starting in 1-2 weeks. I think it should be fairly straight-forward, the biggest challenge will probably be setting up the database/applying the schema using the persistence cli tools.
The text was updated successfully, but these errors were encountered: