You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's great that we have example Helm Charts from #1233,
But it would be much nicer if it was set up as a Helm Repository or an OCI (maybe it is and I can't find it). This way I can
Retrieve the Charts with helm repo add / update {repo}
Manage it as a dependent Subchart with helm dependency update
Lots of folks use a GitHub Pages URL as their Helm Repository URL
I manage about 20 other cluster operators (from Crossplane to Argo) and they all facilitate Helm Subcharting by hosting a Helm Repository. Most of them have official entries on artifact.io
Is your feature request related to a problem? Please describe.
The problem is the difficulty when installing Skipper in Kubernetes using Helm. You've done the hard part by designing/documenting generic templates. Please go the extra mile by packaging an official repository that is discoverable on artifact.io.
Describe the solution you would like
By hosting your own Helm Repository, you make life way simpler for those of us consuming your Helm Charts -- especially as it pertains to change management via Helm Subcharts
Describe alternatives you've considered (optional)
Not sure there are any when using Helm
Additional context (optional)
Thank you for your consideration
Would you like to work on it?
Yes
The text was updated successfully, but these errors were encountered:
ccmcbeck
changed the title
Provide a official Skipper Helm repository and make it discoverable on artifact.io
Provide official Skipper Helm repository and make it discoverable on artifact.io
Dec 19, 2024
Hi, thanks for reaching out! That would be nice! It was discussed multiple times but we just didn't have the time to create/test the chart. However, we aren't against it; It just doesn't fit in our workflow.
The question is who will maintain the helm chart?
In the past we never added one but linked to some other repository and make clear that it is not us. I think we should not bless one but we are happy to link to another repository. If you want to ask questions about a configuration we are happy to help. If we have it here we will only get questions about some helm configuration which is not easily understandable.
So in general I think I would not recommend that we have a helm chart in our repository.
It's great that we have example Helm Charts from #1233,
But it would be much nicer if it was set up as a Helm Repository or an OCI (maybe it is and I can't find it). This way I can
helm repo add / update {repo}
helm dependency update
Lots of folks use a GitHub Pages URL as their Helm Repository URL
I manage about 20 other cluster operators (from Crossplane to Argo) and they all facilitate Helm Subcharting by hosting a Helm Repository. Most of them have official entries on artifact.io
Is your feature request related to a problem? Please describe.
The problem is the difficulty when installing Skipper in Kubernetes using Helm. You've done the hard part by designing/documenting generic templates. Please go the extra mile by packaging an official repository that is discoverable on artifact.io.
https://artifacthub.io/packages/helm/sinextra/skipper is someone who is trying to fill this void
Describe the solution you would like
By hosting your own Helm Repository, you make life way simpler for those of us consuming your Helm Charts -- especially as it pertains to change management via Helm Subcharts
Describe alternatives you've considered (optional)
Not sure there are any when using Helm
Additional context (optional)
Thank you for your consideration
Would you like to work on it?
Yes
The text was updated successfully, but these errors were encountered: