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

rhdh-local: support specifying registry credentials for OCI artifacts

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

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • RHDH Local
    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      We are using OCI artifacts to distribute our custom plugins. In RHDH deployed via Helm on Azure Kubernetes Service (AKS), we configure the redhat-developer-hub-dynamic-plugins-registry-auth secret with auth.json containing the registry credentials which is mounted as a volume and used by the initContainer to install the dynamic plugins from our internal registry.
      
      We would like rhdh-local to have similar functionality to emulate the process RHDH uses to install dynamic plugins, and so that we can install our custom dynamic plugins from our internal registry as part of local development with rhdh-local.
      
      Describe the impact to you or the business
      Using rhdh-local as our local development environment for RHDH is not 1:1 with our AKS RHDH deployment as we cannot install custom dynamic plugins from our internal registry which requires authentication.

      Version-Release number of selected component (if applicable):

      1.3

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

              rh-ee-bwilcock Ben Wilcock
              rhn-support-dboeren David Boeren
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: