Can you see from kubernetes events what is the error that causes the pod not to be created?
pods are working
i can connect to pod shell, but i can’t connect to nodes shell(control or worker node shell)
pods are working
i can connect to pod shell, but i can’t connect to nodes shell(control or worker node shell)
hello folks, I was facing the same problem here and when checking Lens Logs I did see it was trying to download the kubectl client same version of the Cluster, makes sense, but my VPN was not letting this download, so I manually downloaded the client and put it in ~/Library/Application\ Support/Lens/binaries/kubectl/1.31/ (the version varies) and give it execution permission with chmod and now everything is fine!
Is this still an issue or ???
my version is Lens:2025.9.15.151055
and when trying to open a terminal for a pod … it flickers and hangs
Hello @james.r.johnson,
Could you please share a few more details to help us investigate?
- Your operating system (Windows / macOS / Linux + version)
- Kubernetes cluster type (EKS, GKE, Minikube, etc.)
- Whether the issue happens for all pods or specific ones
- Any errors visible in the Developer Console
We’re also preparing a new release very soon that includes several fixes related to terminal and shell behavior — it might already address what you’re seeing.
Thanks for helping us narrow this down!