CONSOLE-2767 removed the hard-coded managed cluster and updated the backend to accept a cluster list. We should continue the POC to update the console operator so that it reads the managed cluster list from the custom resources contributed by ACM and passes those values to the console backend.

Technical Details:

Once you have ACM installed, the kube api server might be available at:

ManagedClusterInfo > spec.masterEndpoint
ClusterDeployment > status.apiURL (if cluster was provisioned from ACM/Hive)

For a quick list of managed clusters, you could query the projects by this label:

cluster.open-cluster-management.io/managedCluster

ACM has a namespace per managed cluster.

Non-goals:

• Discovering the monitoring public URLs for managed clusters. These are not available in the managed cluster custom resource.

Acceptance Criteria:

• Console operator watches the cluster list and redeploys console with the updated config when the cluster list changes
• The operator passes minimally the cluster name and API server URL to the console backend.
• (Optional) The operator passes the CA file for the cluster to the backend. (If we don't get to this, it can be a follow up story.)

This is only a POC and does not required any code to be merged.