Skip to content
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

Unable to open a shell on cluster's nodes #8182

Open
JulesPichon84 opened this issue Feb 25, 2025 · 3 comments
Open

Unable to open a shell on cluster's nodes #8182

JulesPichon84 opened this issue Feb 25, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@JulesPichon84
Copy link

Describe the bug

When I try to open a shell on one of the nodes in my cluster, the shell cannot connect to the node even though I am able to execute kubectl commands with --kubeconfig passed in the command (on my local machine).

Expected behavior

I can open a shell on a node

Screenshots

Image

Environment (please complete the following information):

  • Lens Version: 2025.2.141554-latest
  • OS: ubuntu-24.04.1-live-server

Thank you for your response !

@JulesPichon84 JulesPichon84 added the bug Something isn't working label Feb 25, 2025
@Tixon123
Copy link

Hello @JulesPichon84,

Thank you for reaching out to Lens support!

Thank you for reporting a bug.

We are working on your issue. Stand by for further updates.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

@panuhorsmalahti
Copy link
Contributor

panuhorsmalahti commented Feb 26, 2025

In Preferences -> Proxy -> Bypass Lens Internal KubeApi Proxy enabled?

@jicowan
Copy link

jicowan commented Mar 2, 2025

I am experiencing a similar issue. Initiating a node shell from the console hangs with Connecting... then finally says, Error occurred: Pod creation timed outfailed to open a node shell: failed to create node pod. If I look at the pods I can see that it started the node-shell pod on the host and if I exec into the pod, I can access the host. I am running Lens 2025.2.141554-latest. I do not have a proxy configured and I haven't needed one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants