feat: Helm Repositories as CRDs

[sim500]

Feature request:

It would be very convenient if the Helm Repositories could be added as custom resources.
So they'd be easily deployable via GitOps methods, without the strict necessity to have a PersistentVolume to keep them persistent.

Do you think it's a feature that could be implement in the next releases?
Or for some reason, using CRDs isn't feasible?

[undera]

I think this is feasible and I heard this suggestion before. But instead of custom resource it feels we can do it via Helm values that would be picked up automatically.

[mainiak]

Hello.

How about integration with Helm Controller which already has CRDs?

• https://docs.k3s.io/helm#using-the-helm-controller
• https://github.com/k3s-io/helm-controller

[undera]

Hello.

How about integration with Helm Controller which already has CRDs?

• https://docs.k3s.io/helm#using-the-helm-controller
• https://github.com/k3s-io/helm-controller

I see Helm Controller has CRD for individual charts, but not for repository. Still it looks doable to load those CRDs and analyze them for repository entries.

A contributor with Golang skills could help us here

[wylswz]

The helm library heavily depends on file system to manage repos/charts. If you were going to do this, will it be like syncing stuff from crd to fs?