Right now, the console operator watches the cluster list and redeploys the console when it changes. This is necessary since the console backend sets up proxies for each spoke cluster and needs to add OAuthClients to the spokes via ManagedClusterAction resources.

If we move to using the ACM cluster proxy, the console backend should no longer need to create its own proxies or set up OAuthClients. This means we have the option to watch the cluster list on the frontend and remove a lot of logic from the operator. It would simplify the code, and the UI would update instantly when the cluster list changes. It would also allow us to potentially support cluster sets or potentially cluster lists that are filtered for the current user's permissions.

We'll need to determine if there are any RBAC limitations. Can normal users watch cluster lists? What resource or resources should we watch?

Acceptance Criteria

• Prototype watching the cluster list on the frontend
• Verify if normal users can watch the cluster list
• Work with the ACM team to determine what APIs to use and identify any gaps
• Document findings