Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-252

Update dynamic plugin references to use OCI artifacts and tagless catalog references

Create Doc EPIC from R...Prepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 33% To Do, 0% In Progress, 67% Done
    • Hide
      When installing dynamic plugins as OCI packages, the `!path` suffix after the OCI reference is no longer needed if the OCI package only contains 1 plugin.
      i.e. oci://my-quay/my-org/my-repo:tagOrSHA!some-plugin-folder-name can now be defined as oci://my-quay/my-org/my-repo:tagOrSHA

      Additionally, the `{{inherit}}` tag can be used to infer the version of the OCI package from an included default dynamic plugin configuration.
      Show
      When installing dynamic plugins as OCI packages, the `!path` suffix after the OCI reference is no longer needed if the OCI package only contains 1 plugin. i.e. oci://my-quay/my-org/my-repo:tagOrSHA!some-plugin-folder-name can now be defined as oci://my-quay/my-org/my-repo:tagOrSHA Additionally, the `{{inherit}}` tag can be used to infer the version of the OCI package from an included default dynamic plugin configuration.
    • Enhancement
    • S

      Part 1: dynamic-plugins.default.yaml

      In RHDH 1.10 or later, the dynamic-plugins.default.yaml must be changed to refer to oci artifacts, instead of local paths (once wrappers are deprecated).

      This depends on:

      • OCI artifact publishing is GA with Konflux, pushing to reg.rh.io (RHEC)
      • documentation to warn about deprecation

      Both of these are set to happen in 1.8.

      Part 2: configmap

      Installation/enablement of dynamic plugins, when referenced in the configmap, should use a tagless/digestless plugin reference from the new plugin catalog

      This depends on

      • updated documentation
      • updated sample configmap
      • existence of a plugin catalog referenced by the helm chart and operator-bundle, installed into the cluster and used to provide the mapping of "tagless plugin reference" to "actual oci artifact"

          1.
          		 Verify Feature Acceptance Criteria are met AND Create Feature Demo Sub-task New Blocker Frank Kong

              rh-ee-frkong Frank Kong
              nickboldt Nick Boldt
              RHDH Cope
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: