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

Pod exec and port-forwarding to Kubernetes don’t work from Lens (After last update) #8113

Open
sm1lexops opened this issue Oct 18, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@sm1lexops
Copy link

sm1lexops commented Oct 18, 2024

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

- name: aleks.org
  user:
    auth-provider:
      config:
        client-id: k8s-authenticator
        client-secret: 
        id-token: 
        idp-issuer-url: https://test-dex.com
        refresh-token: 
      name: oidc

Additional context
when I delete the and unset KUBECONFIG it directly from the Lens integrated terminal, it works as expected.
unset KUBECONFIG

Screenshots

Screenshot 2024-10-18 at 13 59 24

Screenshot 2024-10-18 at 14 03 38

Screenshot 2024-10-18 at 14 02 46

@sm1lexops sm1lexops added the bug Something isn't working label Oct 18, 2024
@clrothmann
Copy link

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.

@clrothmann
Copy link

@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.

@sm1lexops
Copy link
Author

sm1lexops commented Oct 23, 2024

I downloaded the latest version of Lens, but it doesn’t work as well as the previous one.
Screenshot 2024-10-23 at 15 09 03
lens-logs-1729685216762.zip

@wangpf09
Copy link

i have the same problem,just run the command kubectl exec in lens term was also been killed

@sm1lexops
Copy link
Author

updated to the latest version, same bahavior
Lens: 2024.11.131815-latest
Electron: 31.6.0
Chrome: 126.0.6478.234
Node: 20.17.0
© 2024 Mirantis, Inc.
Screenshot 2024-11-28 at 13 56 14

@sm1lexops
Copy link
Author

after I manually changed the path to kubectl, the cli is working, I can run a simple command to get some resources and information about k8s cluster, but still can't execute kubectl exec
Screenshot 2024-12-10 at 19 59 04

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

3 participants