Please publish to OCI

[Ornias1993]

Is your feature request related to a problem?/Why is this needed
OCI is slowly becoming the go-to standard for helm charts.
Having http based charts in-between (over)complicates dependency management.

Describe the solution you'd like in detail
Publish to OCI, for example: GHCR is a viable option

Describe alternatives you've considered

Additional context

[andyzhangx]

@Ornias1993 what do you mean http based charts? current helm chart install is referencing https address, e.g.

helm repo add csi-driver-smb https://raw.githubusercontent.com/kubernetes-csi/csi-driver-smb/master/charts
helm install csi-driver-smb csi-driver-smb/csi-driver-smb --namespace kube-system --version v1.14.0

[Ornias1993]

@Ornias1993 what do you mean http based charts? current helm chart install is referencing https address, e.g.

helm repo add csi-driver-smb https://raw.githubusercontent.com/kubernetes-csi/csi-driver-smb/master/charts
helm install csi-driver-smb csi-driver-smb/csi-driver-smb --namespace kube-system --version v1.14.0

What I mean with http based charts, is every chart system with repo's that are not OCI based.
Https is secure http after-all.

I think that's quite obvious though... As there are only three helm repo options: http(s), file and OCI

---

It's not really relevant either, as i'm requesting OCI distribution.
I just wrote down what is currently used, but that has nothing to do with what this is requesting.

I get the feeling there is a language issue here, so I would suggest offloading to a native english-maintainer...
(as the reference to http was totally irrelevant for the request posted here)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Ornias1993]

/remove-lifecycle stale