Epic Goal

• Provide a User Experience for CRUD-ing the ManagedClusterImageRegistry API in the MCE UX

ManagedClusterImageRegistry documentation:
https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/clusters/managing-your-clusters#imp-clust-custom-image-override 

Why is this important?

• The ManagedClusterImageRegistry API is needed when a custom image registry needs to be defined for a managed cluster to pull agents from a different image repository such as in disconnected scenarios
• The ManagedClusterImageRegistry API allows users to define different image registries for different sets of clusters as sliced across ManagedClusterSet groupings
• The user should be able to easily understand the image registry configurations for their clusters

Scenarios

1. On the ManagedClusterSet details page, the user can:
   • View a list of configured ManagedClusterImageRegistries within the ManagedClusterSet
     • Name, Namespace, Placement reference, Pull Secret reference, # of registries (or should we just list the registries...?)
   • Create a ManagedClusterImageRegistry within the ManagedClusterSet
     • YAML editor support is provided, the ManagedClusterImageRegistry CR is in the editor
     • User can input a name
     • User can select a Namespace that is bound to the ManagedClusterSet (has a ManagedClusterSetBinding to the ManagedClusterSet)
     • User can provide a pull secret for the image registry
       • User just provides the pull secret
       • UI automatically creates the Secret, and configures the reference in the ManagedClusterImageRegistry
       • The Secret is visible in the YAML editor
     • User can input a list of image registries
       • Image registry mirror and source values having client-side validation
     • User can provide a Placement to schedule the ManagedClusterImageRegistry configurations to clusters
       • Re-use the Placement UX in Policy and Application
       • UI automatically creates the Placement, and configures it to the Placement reference in the ManagedClusterImageRegistry CR
       • The Placement is visible in the YAML editor
   • Update an existing ManagedClusterImageRegistry from the table row menu
     • The update experience re-uses the Create form, like other flows
   • Delete an existing ManagedClusterImageRegistry from the table row menu

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• All scenarios are complete

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• 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 Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>