-
Notifications
You must be signed in to change notification settings - Fork 40k
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
kubectl proxy doesn't allow WebSockets #25126
Labels
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
Comments
This was referenced May 4, 2016
Also, turns out one cannot issue |
roberthbailey
added
the
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
label
May 8, 2016
Hi guys, it so funny that this issue is still unresolved. |
Hi @pshirshov, your funny contribution is welcome to fix this issue. |
See #49534 also. |
It appears that #49534 fixed this. |
openshift-publish-robot
pushed a commit
to openshift/kubernetes
that referenced
this issue
Jun 19, 2020
…ing-listener-events apiserver: create LateConnections events on connections in the last 20% of graceful termination time Origin-commit: 2ffb8c490cbf2b7de9661f7821dc8e3c1b586eff
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no specific issue that addresses this issue, which I think is rather critical. I haven't tested SPDY and HTTP/2 yet, but those are probably broken also. In amy environments
kubectl proxy
would be the only user-friendly way to to get to the internal services, although it's understood that it can only carry HTTP traffic, it should support modern uses of HTTP.The text was updated successfully, but these errors were encountered: