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

Exec-ing into pod not working - "Server lost session" #8771

Open
dagobertdocker opened this issue Mar 11, 2024 · 5 comments
Open

Exec-ing into pod not working - "Server lost session" #8771

dagobertdocker opened this issue Mar 11, 2024 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/not-reproducible Indicates an issue can not be reproduced as described.

Comments

@dagobertdocker
Copy link

What happened?

When trying to initiate new terminal session in pod from dashboard, the terminal screen stays black, and a message is displayed "Server lost session".
In the logs, I see

[kubernetes-dashboard-api] 2024/03/11 13:59:01 handleTerminalSession: can't Recv: sockjs: session not in open state

What did you expect to happen?

Interactive terminal session established and shell prompt visible.

How can we reproduce it (as minimally and precisely as possible)?

  1. Deploy Kubernetes Dashboard via helm chart
  2. Navigate to a pod details page
  3. Click "Exec into pod"
  4. Observe "Server lost session" error message

Anything else we need to know?

No response

What browsers are you seeing the problem on?

Firefox

Kubernetes Dashboard version

7.1.2

Kubernetes version

1.26.9

Dev environment

No response

@dagobertdocker dagobertdocker added the kind/bug Categorizes issue or PR as related to a bug. label Mar 11, 2024
@floreks floreks added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/not-reproducible Indicates an issue can not be reproduced as described. labels Mar 12, 2024
@floreks
Copy link
Member

floreks commented Mar 12, 2024

I could not reproduce it based on the provided steps. Tested on Firefox/Chrome and exec works just fine.

@dagobertdocker
Copy link
Author

I upgraded to k8s 1.28.7, and since then, the problem is gone.

@dagobertdocker
Copy link
Author

For future reference:

I am using a setup with HAProxy -> NGINX Inc's Ingress -> gogatekeeper (OAuth2 proxy) -> Kong service of Dashboard.
In the end, I had to whitelist the /api/sockjs path in gogatekeeper (it seems to remove auth headers) to get it to work consistently..

@shnigam2
Copy link

I have this issue on 1.28.5 EKS as well

@dagobertdocker
Copy link
Author

Correction, it does not work consistently, but randomly. So, this issue is open and being tracked in #8838 I assume..

@dagobertdocker dagobertdocker reopened this Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/not-reproducible Indicates an issue can not be reproduced as described.
Projects
None yet
Development

No branches or pull requests

3 participants