-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
3
-
False
-
XCMSTRAT-589 - [Internal Preview] OCM console can connect to regional OCM instances to manage cluster lifecycle
-
-
-
ACM Console Sprint 257
User story:
The region selection dropdown needs to list regions that are supported by the new data sovereign regional CS instances. The wizard needs to track both the cloud provider region selected, and the RH region instance to use for API calls. It may also need to be moved before the name field, so that uniqueness can be validated against the correct API instance.
Acceptance criteria:
- List of regions can be hard-coded in initial implementation, to be replaced with using new provider metadata API when available
- Cluster name validation is performed against correct CS instance
Mockups:
-------------------------------------------------------------------------------------------------------------------------------
Implementation details
The region list will need to be moved before the cluster name (because the cluster name validation requires the region). UX may have an opinion in the exact placement.
Just to clarify, there isn't going to be two region drop-downs only a single dropdown that contains AWS regions that support both HCP and regionalized clusters.
In order to build the region list(s) we will need to continue to use both the "/api/clusters_mgmt/v1/cloud_providers?size=-1&fetchRegions=true" endpoint to get all the available regions and any additional information. In addition, we will need to use 'https://api.stage.openshift.com/static/ocm-shards.json' (for now) to get the correct regional information (including URLs that will provision the cluster)
See https://redhat-internal.slack.com/archives/C060DSUC51S/p1716296061123079?thread_ts=1709137611.221749&cid=C060DSUC51S for the disucssion.
- blocks
-
OCMUI-2117 [OCMUI][Data sovereignty]User allowed to bypass the Cluster name & domain prefix validation from Wizard
-
- Closed
-
- links to
- mentioned on