-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Cannot exec into a pod when using tsh proxy kube
: Failed writing kube error response body: http: connection has been hijacked
#33020
Labels
Comments
We are seeing this as well. We just upgraded from Teleport 13.3.8 to 14.0.1. We are running on Kubernetes 1.26.4 if that makes any difference. |
tigrato
added a commit
that referenced
this issue
Oct 5, 2023
The header `Connection: close` causes failure in kubetl when it upgrades the connection to SPDY. The `ReadTimeout` and `WriteTimeout` are known to cause problems to Kubernetes watch streams. Fixes #33020 Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 9, 2023
* Header `Connection: close` causes `kubectl` to fail exec The header `Connection: close` causes failure in kubetl when it upgrades the connection to SPDY. The `ReadTimeout` and `WriteTimeout` are known to cause problems to Kubernetes watch streams. Fixes #33020 Signed-off-by: Tiago Silva <tiago.silva@goteleport.com> * add unit tests --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
github-actions bot
pushed a commit
that referenced
this issue
Oct 9, 2023
The header `Connection: close` causes failure in kubetl when it upgrades the connection to SPDY. The `ReadTimeout` and `WriteTimeout` are known to cause problems to Kubernetes watch streams. Fixes #33020 Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 10, 2023
* Header `Connection: close` causes `kubectl` to fail exec The header `Connection: close` causes failure in kubetl when it upgrades the connection to SPDY. The `ReadTimeout` and `WriteTimeout` are known to cause problems to Kubernetes watch streams. Fixes #33020 Signed-off-by: Tiago Silva <tiago.silva@goteleport.com> * add unit tests --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior:
After starting a kube proxy and pointing my KUBECONFIG at the generated file, I should be able to exec into a pod.
Current behavior:
After starting a kube proxy and using its KUBECONFIG, kubectl exec fails with
Error from server:
and in the server logs I see this:Originally reported on community Slack, I was able to reproduce it.
Bug details:
The text was updated successfully, but these errors were encountered: