Closed barddes closed 2 years ago
Probably my issue is related to #4506 and #4442.
even i have the same issue
Yes, thanks for the report. But it is indeed a duplicate of those. You can fix this issue temporarily by deleting ~/.config/Lens/lens-local-storage/<CLUSTER-ID>.json
Describe the bug When connecting to the cluster, the app chash showing two stacks on screen: component stack and error stack. While on this state, I cannot navigate the cluster as the stacktrace covers the whole screen. I also tried to connect to another cluster. It connected successfully without any issue.
Deleting ~/.k8slens and ~/.config/OpenLens temporally fix the problem.
To Reproduce I have encountered this issue a few times by now, but I'm still unable to reproduce it flawlessly.
The steps did when the error happened for the first time:
Expected behavior Navigate through the cluster, check pods and logs, etc.
Screenshots Unafortunally I've lost the screenshot, if/when it happen again I'll upload it
Environment (please complete the following information):
Logs: When you run the application executable from command line you will see some logging output. Please paste them here:
I compared the error logs with the logs when I've already deleted the mentioned folders (fixed the problem), they are the same :(
Kubeconfig:
Additional context RKE Cluster