You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
My device ran out of battery multiple times over night (was at 100% before and then unplugged and lid closed for device sleep).
I was surprised that lens is taking an insane amount of resources when not able to authenticate against EKS.
To Reproduce
Steps to reproduce the behavior:
Use AWS with SSO
Connect to a cluster, use lens for some time
Let your authentication token for SSO expire
See how lens goes crazy with resources and eats up battery in sleep when the auth token expired over night
Expected behavior
On authentication fail (3x in a row?) a user should be hitting a retry button instead of retrying to infinity.
Same goes for failing requests to the kubernetes api, as these seem to also be causing it.
Screenshots
Battery graph of MacOS (i swear i wasn't working at night):
Logs visible in Console app:
Environment (please complete the following information):
Lens Version: 2024.11.x
OS: OSX
Installation method (e.g. snap or AppImage in Linux): -
Logs:
Kubeconfig:
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
My device ran out of battery multiple times over night (was at 100% before and then unplugged and lid closed for device sleep).
I was surprised that lens is taking an insane amount of resources when not able to authenticate against EKS.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
On authentication fail (3x in a row?) a user should be hitting a retry button instead of retrying to infinity.
Same goes for failing requests to the kubernetes api, as these seem to also be causing it.
Screenshots
Battery graph of MacOS (i swear i wasn't working at night):
Logs visible in Console app:
Environment (please complete the following information):
Logs:
Kubeconfig:
Additional context
The text was updated successfully, but these errors were encountered: