When connecting to cluster shows progress with "Refreshing cluster accessibility..." message for a minute

[mih-kopylov]

Describe the bug
Each time I connect to a cluster it takes about a minute for Lens to do it. It hangs on the "Refreshing cluster accessibility..."

To Reproduce
Steps to reproduce the behavior:

1. Have the cluster disconnected
2. Click to the cluster
3. See the connecting log, like in the screenshot, that ends with the "Refreshing cluster accessibility..." message

Expected behavior
The connection to the cluster happens within a couple seconds, and I'm able to observe workloads, etc.

Screenshots

Environment (please complete the following information):

• Lens Version: 2024.5.271333-latest
• Chrome: 118.0.5993.159
• OS: Windows
• Installation method: releases binary

Logs:
In lens-main.log there're a lot of lines like this:

warn: [AUTHORIZATION-NAMESPACE-REVIEW]: allowing all resources in namespace="namespace-name" due to incomplete SelfSubjectRulesReview: webhook authorizer does not support user rule resolution

It's because there're lots of namespaces in the cluster that I don't have access to, I guess. And probably that might be the reason why Lens is slowed down on connecting - if it goes through the namespaces list and tries to do something.

[garyhodgson]

Just to add another data point, I have also been experiencing this delay.

I have admin rights to the clusters, so I don't believe it is due to user permissions. Seems like lens takes a while collecting the initial cluster state.