starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3007] [feature]: k8s deployment strategy - Helm Chart #978

New issue

Closed

opened 2026-03-16 17:54:49 +03:00 by kerem · 8 comments

kerem commented

2026-03-16 17:54:49 +03:00

Owner

Originally created by @WDaan on GitHub (Apr 20, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3007

Is there an existing issue for this?

I have searched the existing issues

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.

Originally created by @WDaan on GitHub (Apr 20, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3007 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Hoppscotch should have an easy-to-get-started Helm chart available to further drive the self-hosting adoption. (I did find [this](https://artifacthub.io/packages/helm/deliveryhero/hoppscotch) one but it seemed rather outdated) I've started with a basic layout [here](https://github.com/WDaan/hoppscotch-helm) 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.

kerem

2026-03-16 17:54:49 +03:00

closed this issue
added the
feature

self-host
labels

kerem commented

2026-03-16 17:55:05 +03:00

Author

Owner

@Breee commented on GitHub (Sep 18, 2023):

We plan to use hoppscotch and host it in k8s.
I would love to help maintaining an official helmchart instead of building a private one.

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 commented on GitHub (Sep 18, 2023): We plan to use hoppscotch and host it in k8s. I would love to help maintaining an official helmchart instead of building a private one. 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

kerem commented

2026-03-16 17:55:10 +03:00

Author

Owner

@WDaan commented on GitHub (Oct 3, 2023):

@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 commented on GitHub (Oct 3, 2023): @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.

kerem commented

2026-03-16 17:55:15 +03:00

Author

Owner

@c-hauwel commented on GitHub (Oct 5, 2023):

@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 commented on GitHub (Oct 5, 2023): @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.

kerem commented

2026-03-16 17:55:20 +03:00

Author

Owner

@WDaan commented on GitHub (Oct 9, 2023):

@c-hauwel Awesome! Did you write your own helm chart for it?

FWIW, i have successfully deployed Hoppscotch in k8s with helm by using a configmap to provide settings instead of an .env

This means we don't have anything blocking us anymore and the hoppscotch team can create a repo to store the helm chart in 😛

@WDaan commented on GitHub (Oct 9, 2023): @c-hauwel Awesome! Did you write your own helm chart for it? > FWIW, i have successfully deployed Hoppscotch in k8s with helm by using a configmap to provide settings instead of an .env This means we don't have anything blocking us anymore and the hoppscotch team can create a repo to store the helm chart in 😛

kerem commented

2026-03-16 17:55:25 +03:00

Author

Owner

@cyberjpb1 commented on GitHub (Oct 24, 2023):

Can you share your installation procedure?

@cyberjpb1 commented on GitHub (Oct 24, 2023): Can you share your installation procedure?

kerem commented

2026-03-16 17:55:30 +03:00

Author

Owner

@BaumMeister commented on GitHub (Feb 22, 2024):

@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.

Hi,

do you mind sharing what you did to be able to run the container(s) as none-root?
I'm facing the same issue.

Regards
Chris

@BaumMeister commented on GitHub (Feb 22, 2024): > @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. Hi, do you mind sharing what you did to be able to run the container(s) as none-root? I'm facing the same issue. Regards Chris

kerem commented

2026-03-16 17:55:35 +03:00

Author

Owner

@kunthar commented on GitHub (Dec 11, 2024):

anyone intend to create helm chart, see #4610

@kunthar commented on GitHub (Dec 11, 2024): anyone intend to create helm chart, see #4610

kerem commented

2026-03-16 17:55:40 +03:00

Author

Owner

@liyasthomas commented on GitHub (Feb 4, 2025):

Hi everyone, thanks for your patience and valuable feedback. This feature has been implemented in the latest release. Please find the official Hoppscotch Helm Charts on GitHub and provide your valuable feedback.

Closing this ticket as this feature is now available in the recent version. Please feel free to reach out if you have any other concerns.

@liyasthomas commented on GitHub (Feb 4, 2025): Hi everyone, thanks for your patience and valuable feedback. This feature has been implemented in the latest release. Please find the official [Hoppscotch Helm Charts on GitHub](https://github.com/hoppscotch/helm-charts) and provide your valuable feedback. Closing this ticket as this feature is now available in the recent version. Please feel free to reach out if you have any other concerns.

kerem referenced this issue

2026-03-17 00:38:25 +03:00

[PR #978] [MERGED] ⬆️ Bump eslint from 7.3.1 to 7.4.0 #2984