-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lens can't open pod or node terminal on single cluster #8128
Labels
bug
Something isn't working
Comments
+1 |
Hello KarooolisZi, Thank you for reaching out to Lens support! Thank you for reporting a bug. Regards, |
Hello @okoshevka, |
bug repeated can't pod exec issues/8113 |
@sm1lexops details are different |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hello, I was upgrading EKS to 1.29 when lens suddenly stopped opening terminals for both nodes and pods. It might be a coincidence because during the process of node groups upgrade, until some point I was still able to drain nodes using node terminal in lens.
After it stopped working, node terminal showed this message:
failed to open a node shell: Unable to start terminal process: CreateProcess failed
Pods terminals showed similar errors to this:
What is interesting, other clusters, which run 1.28 were okay. I also was able to do all the commands from my local terminal for both 1.28 and 1.29 clusters.
I thought that kubectl might be too old so I upgraded my kubectl from 1.27 to 1.29. This also didn't change anything.
On my last step, I reinstalled newest Lens IDE version, which did not help either.
Other clusters I manage are 1.28 and I didn't have issues with them even after this happened on 1.29.
I also got Lens IDE informational message like this:
If terminal shell is not ready please check your shell init files, if applicable.
After trying all of these things I managed to get this error, too:
Error occurred: Pod creation timed outfailed to open a node shell: failed to create node pod
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This should let you enter node terminal or do prepared commands like drain/cordon/uncordon.
Environment (please complete the following information):
Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
Additional details
I checked one issue where you asked whether haproxy or similar tool is being used. In my case, no similar tools are being used.
The text was updated successfully, but these errors were encountered: