Skip to content

Publish Helm Chart #96

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

Closed
m4rcu5 opened this issue Jun 9, 2020 · 1 comment · Fixed by #109
Closed

Publish Helm Chart #96

m4rcu5 opened this issue Jun 9, 2020 · 1 comment · Fixed by #109

Comments

@m4rcu5
Copy link

m4rcu5 commented Jun 9, 2020

Hi,

I see you maintain a Helm Chart in this project, but this is not the same one as published on the Helm Hub (https://hub.helm.sh/charts/stable/katafygio).
Your version also seems to support more features.

Would you like to publish your version to the Helm Hub to make installation easier for users. Especially for tools like K3s' build in Helm implementation, which sources from hosted charts.
Or is your version also hosted on a Chart repository?

Meanwhile I noticed that the version on Helm Hub was broken and I submitted a patch (helm/charts#22494). However I think it would be nicer to have a version of the upstream maintainer there instead.

@bpineau
Copy link
Owner

bpineau commented Nov 30, 2020

Hi,
We'll have to setup our own Helm repository somehow, since Helm Hub is now deprecated and frozen.
Perhaps by setting up the helm Github Actions to publish with github (https://github.com/helm/charts-repo-actions-demo).

bpineau added a commit that referenced this issue Dec 1, 2020
Use Github Actions and gh-pages to self host charts, since Helm Hub
is deprecated and frozen. Should resolve #96 .
bpineau added a commit that referenced this issue Dec 1, 2020
Use Github Actions and gh-pages to self host charts, since Helm Hub
is deprecated and frozen. Should resolve #96 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants