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
[feature]: k8s deployment strategy - Helm Chart #3007
Comments
We plan to use hoppscotch and host it in k8s. let me know if you need help with anything - In addition i would like to add out of the box support for ingress using certmanager CRs for Certificates, externalDNS CRs for dnsendpoints and traefik CRs for ingressroutes |
@Breee Great! There are still a couple of things that need to be worked out. I haven't followed up with this project in a while. Last I checked I remembered that we still could not set ENV's dynamically for the frontend, making self-hosting on k8s not really viable as you'd have to rebuild the frontend yourself. I think we should start by creating a new git repo in this org to store the helm chart. I'm more than happy to transfer mine if that could be a usefull starting point. |
@WDaan Hi, FWIW, i have successfully deployed Hoppscotch in k8s with helm by using a configmap to provide settings instead of an .env file. Also, I had to rework the images to run as non-root user, as the policies in our clusters doesn't allow root user (which seems to be the best practice nowadays). Now the pods are up and running but i'm plagued with CORS issues. Edit: CORS issues solved by adding "nginx.ingress.kubernetes.io/cors-allow-..." annotations in the ingress definition. |
@c-hauwel Awesome! Did you write your own helm chart for it?
This means we don't have anything blocking us anymore and the hoppscotch team can create a repo to store the helm chart in 😛 |
Can you share your installation procedure? |
Hi, do you mind sharing what you did to be able to run the container(s) as none-root? Regards |
Is there an existing issue for this?
Summary
Hoppscotch should have an easy-to-get-started Helm chart available to further drive the self-hosting adoption. (I did find this one but it seemed rather outdated)
I've started with a basic layout here and would gladly transfer over that repo to the hoppscotch org. (I included Docker container publishes for those 3 components as well, but think these should be move to this main repository)
It's not by any means perfect but it's a good start.
I do believe there is one thing lacking to get this working and that's dynamic env support. As far as I can tell from the docs, you need to build locally with your
.env
-values already configured. This is very hard/cumbersome to accomplish if you're running in a k8s environment.Let me know what you think and if you need any help!
Why should this be worked on?
As hoppscotch is getting self-hosted support, a key part of this is being able to run the stack on Kubernetes. And as we now already have 3 components, it's becomes a bit harder to setup. Therefore, an easy to configure Helm Chart template is crucial.
The text was updated successfully, but these errors were encountered: