Create Helm chart repository for this project. about external-secrets HOT 6 CLOSED

As discussed in the community meeting, we should the name External Secrets Operator for the Helm chart.

from external-secrets.

Did you think something about repository?
It would be nice to have ESO and KES under the same repo but it also adds quite a bit of hassle to set that up and would be nice if the projects remained separated so KES can be deprecated😄

I'm not really sure how the organisations work on artifacthub but I have an organisation called external-secrets there, where I migrated the KES chart after the deprecation of helm hub.

Ping me with usernames on artifacthub and I can add you to the org when that's relevant

from external-secrets.

I had some free time this weekend and gave a shot at this:

https://github.com/external-secrets/helm-charts

I set used github pages as suggested.

@Flydiverny how do you suggest to use artifacthub and what the advantage would be?

The repo is already live and can be used as follows:

➜ helm repo add external-secrets https://external-secrets.github.io/helm-charts/
➜ helm search repo external-secrets
NAME                             	CHART VERSION	APP VERSION	DESCRIPTION                              
external-secrets/external-secrets	0.1.1        	0.1.0      	External secret management for Kubernetes

There is no release automation for this yet but frankly, I am not sure is necessary yet. Depending on how often releases will happen it might be worth it.

One thing that needs to be decided is where the chart should reside. Currently, I copied the chart from the main repository but we should avoid this to prevent drift. If we decide to go forward with this there are two additional tasks:

• update documentation to use the new charts repo url
• consider using the CNAME as suggested: charts.external-secrets.io

Looking forward to your feedback.

from external-secrets.

@riccardomc I think the only benefit of artifacthub is increased discoverability. We had someone point out it was referring to the old godaddy repo in the past. which is why I made the owner claim there. Think anyone could add any repo there for it to be indexed and searchable. But seems the repo names are unique anyway.

from external-secrets.

We might also consider using this github action: https://github.com/helm/chart-releaser-action

from external-secrets.

+1 for artifacthhub ✨

One thing that needs to be decided is where the chart should reside.

Let's discuss that on wednesday. IMHO we should serve both docs and helm chart via github pages from this repo. But we need to be careful not overriding the helm index. I found out ingress-nginx does it exactly that way (1 / 2 / 3).

from external-secrets.