Skip to content

Installing charts from OCI Registry #660

Closed

Description

@mittler-works

Hi and thank you for this tool,

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:
Image

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?

Activity

  1. undera commented on Mar 3, 2026

    @undera
    Collaborator

    Hi
    How do you do that in pure Helm CLI?

  2. mittler-works commented on Mar 3, 2026

    @mittler-works
    Author

    I've installed above chart (mongodb chart from cloudpirates) via cli using this command:

    helm install -n mongodb mongodb oci://registry-1.docker.io/cloudpirates/mongodb -f values.yaml
    

    and I do upgrades using

    helm upgrade -n mongodb mongodb oci://registry-1.docker.io/cloudpirates/mongodb -f values.yaml
    

    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.

  3. mittler-works commented on Mar 3, 2026

    @mittler-works
    Author

    I also tried other charts on docker. Likewise I tried other registries. Unfortunately, none of my attempts were successful.

  4. added a commit that references this issue on Mar 17, 2026
    106c012
  5. undera commented on Mar 17, 2026

    @undera
    Collaborator

    I'm adding a button to install from URL
    Image

    And switch for URL when reconfiguring:

    Image

    @mittler-works Would that be sufficient for your workflow?

  6. mittler-works commented on Mar 17, 2026

    @mittler-works
    Author

    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.

  7. undera commented on Mar 17, 2026

    @undera
    Collaborator

    I tried to look for a way, but it seems that Helm does not save in metadata the origin of installed release.

  8. added a commit that references this issue on Mar 17, 2026
    123f674
  9. mittler-works commented on Mar 18, 2026

    @mittler-works
    Author

    (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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂ 换网址