Uploaded image for project: 'Helm'
  1. Helm
  2. HELM-360

Support OCI flow in ODC

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Helm, UI
    • Support OCI flow in ODC
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Problem:

      We need to enable users to install their charts from OCI registries. At the moment ODC only supports Helm repos but with OCI support we now have another options user can use to store and source their charts. These are the registries that support OCI today: https://helm.sh/docs/topics/registries/#helm-repositories-in-oci-based-registries. Quay seems to also be supported: https://github.com/opencontainers/artifacts/blob/main/implementors.md

      Goal:

      Support OCI flow in ODC

      Why is it important?

      OCI is becoming the standard to manage charts for some companies. Having parity with helm CLI is the main goal here.

      Use cases

      #User can initiate a helm install by passing full path to helm in registry.
      #User will be given the option to install a specific version of the chart passed in the registry
      #User will be able to upgrade a chart passing a different version

      Acceptance criteria

      1. ODC allows for helm charts to be install and upgraded from an OCI compatible registry
      2. New downstream documentation will be required to walk the user through installing from registry
      3. Test Cases are implemented to cover the OCI registry path

      Dependencies (External/Internal)

      Design Artifacts

      TBD: New spike story should yield a document that will be reference here when available

      Exploration

      Note

              Unassigned Unassigned
              dperaza@redhat.com David Peraza
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: