• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Catalog, Helm Chart, Operator
    • None
    • Multi-Source Plugin Catalog Support
    • S
    • False
    • Hide

      None

      Show
      None
    • False
    • RHDHPLAN-335Support several plugin catalogs in the Extensions plugin
    • To Do
    • RHDHPLAN-335 - Support several plugin catalogs in the Extensions plugin
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 100% To Do, 0% In Progress, 0% Done

      EPIC Goal

      Update the RHDH init container, Helm chart, and Operator to support configuring and extracting multiple plugin catalog OCI images to separate subdirectories under /extensions.

      Background/Feature Origin

      Single plugin catalog support via CATALOG_INDEX_IMAGE is already implemented. The init container extracts the contents of the plugin catalog OCI image to /extensions, and the catalog backend module recursively scans that directory for Plugin/Package catalog entity YAML files.

      This epic extends that capability to support multiple catalog sources. The backend already supports multiple sources implicitly (recursive glob of /extensions/{}/{*}.yaml), so only the init container and deployment configs need changes.

      Why is this important?

      • Flexibility: Organizations can combine official RHDH plugins with community and internal plugins
      • Separation of concerns: Allows community plugins to be distributed via separate catalog without modifying RHDH core
      • Enterprise customization: Customers can add proprietary/internal plugin catalogs alongside supported plugins

      Out of Scope

      Merging dynamic-plugins.default.yaml from multiple sources is out of scope for this epic, only the primary/first catalog source provides dynamic-plugins.default.yaml (plugin installation configurations). Additional sources contribute only catalog metadata (Plugin/Package YAMLs for the Extensions UI). Merging default configs from multiple sources may be considered in a future enhancement.

      User Scenarios

      Dependencies (internal and external)

      Acceptance Criteria

      Release Enablement/Demo - Provide necessary release enablement details
      and documents

      DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
      Issue>

      DEV - Upstream documentation merged: <link to meaningful PR or GitHub
      Issue>

      DEV - Downstream build attached to advisory: <link to errata>

      QE - Test plans in Playwright: <link or reference to playwright>

      QE - Automated tests merged: <link or reference to automated tests>

      DOC - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              rh-ee-hhadfiel Hope Hadfield
              RHDH Install
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: