Publish blob-csi-driver Helm chart to alternative registry (OCI / Helm repo)

[imranrazakhan]

Hi,

Our organization is currently trying to deploy the Helm chart for the CSI Blob driver, but we are facing a restriction due to internal security policies.

We are not allowed to pull Helm charts directly from GitHub raw URLs, specifically:

https://raw.githubusercontent.com/kubernetes-sigs/blob-csi-driver/master/charts

Because of this, we cannot consume the chart as a dependency in our production environments.

---

Request

Would it be possible to publish the Helm chart to an alternative, standard distribution location such as:

• An OCI registry (recommended)
Example:
oci://ghcr.io/...

Why this helps

Many enterprises (including ours) block direct access to:

• raw.githubusercontent.com
• arbitrary GitHub content endpoints

But allow:

• OCI registries
• curated Helm repos
• artifact repositories (JFrog, Nexus, etc.)

Publishing the chart via OCI would make it much easier for enterprise users to adopt and automate deployments.

[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