Stop using raw.githubusercontent as chart repository

[AlexDaciuk]

Is your feature request related to a problem?/Why is this needed

As is already know for a few days, Github is aggressively blocking what they call "scrapping" in raw.githubusercontent.com, making installation of this chart using the documentation URL fail with Error: 429 Too Many Requests

GitHub Community posts with users with the same issue (Error: 429 Too Many Requests when trying to access anything in raw.githubusercontent.com)

• https://github.com/orgs/community/discussions/177971
• https://github.com/orgs/community/discussions/178024

Describe the solution you'd like in detail
Migrate to a different solution for chart hosting (Github Pages, ArtifactHub, GHCR ) that supports anonymous charts download

Additional context

All of my chats that are hosted using Github Pages (https://.github.io/-charts) works without any issue

I suspect the fact that my ISP uses CGNAT is not helping the issue

I install csi-driver-nfs to my cluster using ArgoCD and I have been hit with the 429 error lately, is not urgent as is my homelab

[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

[mkilchhofer]

I would really appreciate if we can move directly to OCI artifacts and push the charts to either registry.k8s.io/ (where the nfsplugin container image is located) or ghcr.io.

OCI method is now a standard to distribute helm charts. I already pushed several projects to do so using this motivation text:

In Helm 3.8+ the OCI method went GA:

• https://blog.bitnami.com/2023/04/httpsblog.bitnami.com202304bitnami-helm-charts-now-oci.html?m=1
• https://helm.sh/docs/topics/registries/
• https://github.com/helm/helm/releases/tag/v3.8.0

I'd like to push the packaged Helm charts also on ghcr.io so we can pull/install the helm chart like this:

helm install my-release oci://registry.k8s.io/csi-driver-nfs/charts --version x.y.z

The NFD (node feature discovery) from Kubernetes SIGs already implemented that via:

• Request: Upload Helm chart to OCI registry kubernetes-sigs/node-feature-discovery#2091
  • docs/deployment: instruct users to use the OCI Helm repo kubernetes-sigs/node-feature-discovery#2301
  • helm: add artifacthub metadata file to OCI registry kubernetes-sigs/node-feature-discovery#2297

Maybe this can be an inspiration to implement it here as well :)