Connecting to MKE cluster through MCC Lens extension spams login redirects in the web browser

[dvirassamy]

Describe the bug
When connecting to MKE clusters through the MCC Lens extension, a redirect to MCC UI is realized for login purposes (through SSO).
However, when the cluster gets disconnected, Lens tries to reconnect indefinitely, which has as a result that the browser is spammed with MCC login redirects.

To Reproduce
Steps to reproduce the behavior:

1. Go to Lens Extension and add @mirantis/lens-extension-cc
2. Click on the Lens extension on the top right and connect to an MCC instance. This will sync all MKE clusters managed by the MCC instance
3. Click on Cluster Catalog and connect to a MKE cluster managed by MCC
4. Login in to MCC through the redirect page
5. Wait for the cluster to get disconnected after some time
6. See multiple redirect pages after multiple reconnect retries by Lens

Expected behavior
I would expect Lens to gradually increase the connect retry period and at some point to stop trying to reconnect to the cluster after a given number of retries.

Screenshots

Environment (please complete the following information):

• Lens Version: 2023.1.110749-latest
• OS: 13.1 (22C65)
• Installation method (e.g. snap or AppImage in Linux): Lens dmg
• MCC Lens extension: 5.3.0

Logs:

Kubeconfig:

Additional context

[stefcameron]

Note that in this scenario (and in v5.3.0 of the extension), the cluster token is short-lived, so it lasts, I think, ~20 minutes before needing to be renewed. Since the extension uses kube-login to get the token to Lens upon opening a cluster synced by the extension into the Lens Catalog.

So it's somewhat easy to get into this scenario, and if Lens is left running on a system over a weekend, it'll just sit there and keep opening browser windows all weekend long. So you come back, and you have potentially hundreds of windows open...

I, too, believe Lens should have a de-escalation algorithm to exponentially taper off to no longer trying to auto-connect.