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

Implement solution for mirroring OCI artifacts into an airgapped RHDH deployment

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

    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 33% In Progress, 67% Done
    • Hide
      Added support for mirroring Red Hat Developer Hub dynamic plugin OCI artifacts to disconnected/airgapped environments. A new mirror-plugins.sh script enables users to mirror dynamic plugins from the official RHDH plugin catalog to their internal registries. The script supports multiple plugin sources including catalog index resolution (--plugin-index), file-based plugin lists (--plugin-list), and direct OCI URLs (--plugins).

      For fully disconnected environments, the script provides a two-phase workflow: first exporting plugins to a local directory (--to-dir) on a connected host, then importing from that directory (--from-dir) to an internal registry on the restricted network. The script automatically rebuilds the catalog index with updated registry references and generates a rhdh-plugin-mirroring-summary.txt mapping file for easy reference when configuring RHDH deployments. This solution is installation-method agnostic and works with both Operator and Helm deployments on OpenShift and Kubernetes platforms.
      Show
      Added support for mirroring Red Hat Developer Hub dynamic plugin OCI artifacts to disconnected/airgapped environments. A new mirror-plugins.sh script enables users to mirror dynamic plugins from the official RHDH plugin catalog to their internal registries. The script supports multiple plugin sources including catalog index resolution (--plugin-index), file-based plugin lists (--plugin-list), and direct OCI URLs (--plugins). For fully disconnected environments, the script provides a two-phase workflow: first exporting plugins to a local directory (--to-dir) on a connected host, then importing from that directory (--from-dir) to an internal registry on the restricted network. The script automatically rebuilds the catalog index with updated registry references and generates a rhdh-plugin-mirroring-summary.txt mapping file for easy reference when configuring RHDH deployments. This solution is installation-method agnostic and works with both Operator and Helm deployments on OpenShift and Kubernetes platforms.
    • Feature
    • M
    • Proposed

      Need a solution for both helm and operator deployments on both OCP and k8s that can handle mirroring OCI artifacts into the cluster for airgap deployments.

      This ought to be able to run in two modes:

      • just the plugins I want to specify, or
      • all the plugins in the catalog

      Depends on

      Should not rely on floating tags, eg., `:1.8` but instead should be able to ask the cli tool to pull all/specific/regex-matched plugins for a given RHDH release (1.y. or 1.y.z?), which would discover the plugins by pulling the catalog image and extracting the json/yaml

          1.
          		 Verify Feature Acceptance Criteria are met AND Create Feature Demo Sub-task In Progress Blocker Fortune Ndlovu

              rh-ee-fndlovu Fortune Ndlovu
              nickboldt Nick Boldt
              RHDH Install
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: