You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to install and manage Helm Charts hosted on an OCI Registry, e.g. oci://registry-1.docker.io/cloudpirates/mongodb
Installing charts from OCI via command line (helm install ...) works with no problems. But I cannot add any OCI Registry to helm-dashboard.
If I try, for example, adding it as a repository, I see the following error:
Yeah, I know, an OCI Registry is not a ChartMuseum Repository, so this is kind of expected. But is there any other way to install and manage Charts from an OCI Registry?
Hi @undera
for my workflow, this would be perfectly sufficient for now, thank you very much! 🎉
In the future, it would be incredibly useful if URLs could somehow be added as a source, so that helm-dashboard could also notify about updates. However, that would be a bigger change, which would obviously require a lot of work.
(Just Brainstorming)
Getting metadata about the origin of an installed release is one problem to face. One way to address this could be to save this information elsewhere (e.g. in helm dashboard data directory or in a crd or whatever). This could be saved either automatically when installing a chart through helm-dashboard or it could be saved manually for already installed releases.
Other problems to face are
trusted and/or private registries that require login.
this would require helm-dashboard to save the credentials somewhere in a safe place
Querying a OCI Registry for available Tags.
I think there is no way to do this with native helm right now
This would require some kind of workaround
So I think, this would be a cool feature. Maybe let's create another issue for it for the backlog? It would be super useful in my workflows so maybe I can have a look on it in some spare time.
Activity
undera commentedon Mar 3, 2026
Hi
How do you do that in pure Helm CLI?
mittler-works commentedon Mar 3, 2026
I've installed above chart (mongodb chart from cloudpirates) via cli using this command:
and I do upgrades using
I can also see the installed release in helm-dashboard, but I cannot reconfigure or update it via helm-dashboard.
I am using Helm Version v4.1.0.
mittler-works commentedon Mar 3, 2026
I also tried other charts on docker. Likewise I tried other registries. Unfortunately, none of my attempts were successful.
feat: add support for installing and upgrading charts from URLs
undera commentedon Mar 17, 2026
I'm adding a button to install from URL

And switch for URL when reconfiguring:
@mittler-works Would that be sufficient for your workflow?
mittler-works commentedon Mar 17, 2026
Hi @undera
for my workflow, this would be perfectly sufficient for now, thank you very much! 🎉
In the future, it would be incredibly useful if URLs could somehow be added as a source, so that helm-dashboard could also notify about updates. However, that would be a bigger change, which would obviously require a lot of work.
undera commentedon Mar 17, 2026
I tried to look for a way, but it seems that Helm does not save in metadata the origin of installed release.
feat: install and upgrade charts from URLs (#663)
mittler-works commentedon Mar 18, 2026
(Just Brainstorming)
Getting metadata about the origin of an installed release is one problem to face. One way to address this could be to save this information elsewhere (e.g. in helm dashboard data directory or in a crd or whatever). This could be saved either automatically when installing a chart through helm-dashboard or it could be saved manually for already installed releases.
Other problems to face are
So I think, this would be a cool feature. Maybe let's create another issue for it for the backlog? It would be super useful in my workflows so maybe I can have a look on it in some spare time.