This epic covers general console support for data sovereignty in pages not covered by other epics. The cluster list and cluster details pages have their own epics.

The scope of this epics includes:

• New feature flag for data sovereignty

We plan to create a feature flag for this work and integrate changes often. The effort is too large to try to merge in the end as one commit. We’ll need to regression test carefully to avoid breaking the general OCM UI as we refactor the code to support data sovereignty.

• Dashboard page

The OCM overview page is built using the data from the summary_dashboard endpoint for an organization in AMS. As cluster metadata is scrubbed from global AMS, this endpoint might not be able to provide data for the entire fleet. We are working on a POC to explore what to do with this page.

• Archived cluster list

The OCM UI also supports showing “archived” (deleted) clusters. Today this data is only stored in AMS subscriptions. Cluster are hard deleted in Cluster Service.

The OCM UI will need a new API to get the archived cluster list once cluster metadata is scrubbed from AMS. This work is being tracked by OCM-6683.

• ROSA wizard

The wizard will need to be updated to use the correct OCM instance for the selected region during ROSA HCP cluster creation. Other wizards will not need to change since they will continue to use the current global Cluster Service.

Cluster name validation will need to check uniqueness for the selected region since cluster names are no longer globally unique. If the region changes, the cluster name will need to be reevaluated.