-
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
Pod exec and port-forwarding to Kubernetes don’t work from Lens (After last update) #8113
Comments
Thank you for reaching out @sm1lexops, and for your time! We appreciate it! Could you please let us know your Lens version of your mentioned last update? Looking forward to your response. |
@sm1lexops We recommend to download the latest version of Lens from our website. We recently released a major update that changes completely the UI/UX, and fixes a lot of this issues. This new version is not yet accessible by checking updates in-App, only downloading from the website. |
I downloaded the latest version of Lens, but it doesn’t work as well as the previous one. |
i have the same problem,just run the command |
Describe the bug
I am unable to execute commands in pods or use port-forwarding via Lens GUI or Lens’ integrated terminal CLI (after last update).
To Reproduce
Steps to reproduce the behavior:
1. Open Lens.
2. Navigate to the desired pod in the Pods section.
3. Click on Pod Shell or Attach to Pod.
4. Attempt to exec into the pod.
error output:
exec /usr/local/bin/kubectl exec -i -t -n gitlab-ci gitlab-runner-5d48dc4f94-2j8kr -c gitlab-runner -- sh -c "clear; (bash || ash || sh)" ✔ │ aleks.com ⎈ error: unable to upgrade connection: error dialing backend: read tcp 192.168.101.120:60692->xx.xx.xx.xx:443: read: network is down Terminal will auto-close in 15 seconds ...
same when try to port-forward:
All is working from local env terminal CLI
Port Forwarding Error occurred starting port-forward, the local port may not be available or the pod devops-atd-qa1-d56b6f558-jhhjk may not be reachable
Expected behavior
exec to pod or port-forward success
Environment (please complete the following information):
• macOS 14.x, 15.x (desktop)
• Linux Ubuntu 24.04 (desktop)
Kubeconfig:
Using OIDC Dex
Additional context
when I delete the and unset KUBECONFIG it directly from the Lens integrated terminal, it works as expected.
unset KUBECONFIG
Screenshots
The text was updated successfully, but these errors were encountered: