Provide official Skipper Helm repository and make it discoverable on artifact.io

[ccmcbeck]

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

1. Retrieve the Charts with helm repo add / update {repo}
2. 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.

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

[MustafaSaber]

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.

Would you like to work on it?
Yes

You can check how we deploy skipper in https://github.com/zalando-incubator/kubernetes-on-aws/tree/dev/cluster/manifests/skipper. Please create a PR and we will be happy to review & extend!

[szuecs]

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.

So I would veto adding a helm chart.

[ccmcbeck]

This saddens me since I'm a big Skipper fan -- been using it for 5+ years.

The question is who will maintain the helm chart?

Well...every other K8s component I use either maintains its own charts or has someone like Bitnami stand in the gap. The key on artifact.io is to have Zalando's official blessing so folks can install with confidence.

If you have intimate product knowledge (which all of you guys have), building and maintaining a Helm chart is fairly trivial.

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

There are other ways to package and deploy K8s components, but Helm 3 seems like the de facto approach. When you package your component for your community, you remove so much up-front friction for folks who just want to try out your great product.

Thank you for considering my issue. Good to know you will help me package it myself.

[szuecs]

Formerly someone of the community maintained a chart and we linked it.
Maybe that's a way to make it happen?

There are a lot of tools that could package it picking one is hard. Skipper is also useful without kubernetes so I think there would be a gap between support and it will duplicate the operations docs and support.
I think it is not sustainable for the project. Better would be to invest more into docs if needed.
Do you think we should document some parts better than we have?