-
Epic
-
Resolution: Won't Do
-
Critical
-
None
-
None
-
Pull secret enhancements for cluster import UX
-
False
-
None
-
False
-
To Do
Epic Goal
- Improve the User Experience when importing *ks clusters that require additional steps to configure a pull secret
Why is this important?
- *ks clusters have additional required steps to allow the cluster to pull images from the Red Hat registry
- When the pull secret is not defined, the cluster will fail to import due to failure to deploy the Klusterlet and add-ons
Scenarios
- Display a warning message to the user on the Import cluster page when a pull secret is not configured.
- Make clear this is a warning message only for *ks cluster import
- The pull secret can be defined in two ways:
- Globally via the MultiClusterHub CR (https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/install/installing#advanced-config-hub )
- Most users will not have RBAC permissions to the MCH, so the UI will have to use the Console ServiceAccount, and send a true/false to the front-end if it is configured. Do not forward the entire MCH object to the front-end.
- Per ManagedClusterSet via ManagedClusterImageRegistry CR (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 )
- Globally via the MultiClusterHub CR (https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/install/installing#advanced-config-hub )
- Display a similar warning message from (1) on the cluster list/details page when a cluster is sitting in Pending import state
- If a user imported the cluster from the CLI, and didn't see the warning message from the UI; we may want to still provide this warning in the console if they go to it to look for any details or hints.
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)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>