Description of problem:

This issue hits users  with a clusters huge number (~ 10k) visibility and with multiregion feature enabled. If such a user goes to cluster list page, very likely the total number of cluster will take a little to be entirely loaded in the app. But if the user don't wait all the loading finishes and clicks on another page link, very likely the new page will take a little to be actually loaded. In such circumstances the app will seem stuck.

How reproducible:

Not always, it depends from the total number of clusters and probably network/banckend conditions.

Steps to Reproduce:

1. Open OCM UI staging.
2. Append in the url "?multiregion=true" (related feature flag has to be enabled too)
3. Go to the cluster list page
4. Wait few seconds
5. Click on another page link (ex: Dashboard, Overview, etc.)
6. Observe the result

Actual results:

At step 6 the cluster list page is still shown for a while, then the requested page is shown.

cl_responsiveness.webm

Expected results:

The page switch should be fast enough.