Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-2449

Onboard new RHDH plugin registry container(s) to Konflux

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • 1.4
    • 1.3
    • Build, Dynamic plugins
    • None
    • Onboard new RHDH plugin registry container(s) to Konflux
    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • RHIDP-4048Konflux build pipelines
    • To Do
    • RHIDP-4048 - Konflux build pipelines
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 0% To Do, 100% In Progress, 0% Done
    • RHDH Core Team 3259

      EPIC Goal

      What are we trying to solve here?

      Onboard new RHDH plugin registry container(s) to Konflux, because OSBS is being sunset and Konflux is the way.

      Background/Feature Origin

      Part of RHIDP-1809, support for external plugins in RHDH from a registry

      Why is this important?

      We need a continuity plan to continue to be able to build RHDH containers in 2025.

      Customers want to be able to install plugins into their RHDH instance, and have the ability to develop their own content internally to their corp. We want to support the idea of having access to multiple registries (community, RH-supported/validated, and private registries too)

      User Scenarios

      Dependencies (internal and external)

      Acceptance Criteria

            nickboldt Nick Boldt
            nickboldt Nick Boldt
            RHIDP - Core Platform
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: