Register Helm chart for artifacthub.io
See original GitHub issueI suggest we make some minor tweaks to make this a Helm chart allowed to be published at artifacthub.io like the dask
and daskhub
helm chart: https://artifacthub.io/packages/search?ts_query_web=dask
I perceive this as the go-to place to present Helm charts to a wide audience after the helm/charts repo got deprecated. To be published there, one should register a new Helm chart registry under the Dask organization.
I’m not sure, have someone created a Dask organization there? If not, do so! I’m not sure what makes the dask
and daskhub
show up under the Helm
organization as they currently do though. Anyone with clues about that?
As reference, note that one can also request to become verified and official to stand out a bit better.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Artifact Hub
Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects.
Read more >How to pull Helm charts from artifacthub.io through Artifactory?
Navigate to the chart's page on artifacthub.io. · In case you don't have a Remote Helm Repository in Artifactory pointing to the URL...
Read more >Artifact Hub Helm charts repository
Artifact Hub Helm charts repository. For more information, please visit Artifact Hub.
Read more >Helm Search Hub
Search for Helm charts in the Artifact Hub or your own hub instance. Artifact Hub is a web-based ... You can browse the...
Read more >Helm In Kubernetes — Part 4: Publish Helm Chart To Artifact ...
3. Add chart to Artifact Hub. Go to https://artifacthub.io/ and create an account if you have not done so. Go to Control Panel ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That makes sense to me. When I originally created the dask-gateway helm repo we weren’t publishing the other charts anywhere. Now that we have a place where the other charts live, moving this over seems fine. I don’t think we need to be backwards compatible here, but we should migrate the past versions over to the new location as well.
I think we just need to claim it right, they already migrated it for us.
I’d like to revisit uniting the Dask helm repo and the Gateway helm repo (specifically the helm repo, not the git repo). Currently the
dask/helm-chart
publishes to thegh-pages
branch on that same repo with chartpress. Here on Gateway it publishes to thegh-pages
branch on the placeholder repodask/dask-gateway-helm-repo
.From a user perspective they need to install different helm repos depending on which project they want.
It would be great to have Gateway publish to the
gh-pages
branch ondask/helm-chart
so that everything is together and users only need one helm repo. We can publish to both to maintain backward compatibility.