-
Notifications
You must be signed in to change notification settings - Fork 712
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 appears to break WebSockets #1427
Comments
To reproduce, do this follow K8s Anywhere setup and deploy scope like this:
You should be able to access the app on the following URL and observe error 400 occurring for all of WebSocket requests.
|
@2opremio and I discussed this offline, and it looks like it’s not something we can fix soon, but I’d like to keep it open unless we would like to explicitly document the fact that Scope doesn't work with |
I think there's little point in keeping this issue open when there's an upstream ticket already tracking it. |
That's true, I created this in the process of figuring it out. However, if On Wed, 4 May 2016, 15:53 Alfonso Acosta, notifications@github.com wrote:
|
Hi all, I am getting the same problem. I am not able to access the Is this issue resolved yet? If not, then please provide me some pointers so that I can try to work on it. |
@satyamz the issue has been fixed in Kubernetes 1.8 (see kubernetes/kubernetes#49534). If you are using an older version of Kubernetes, please use |
There is a a little unclear kubernetes/kubernetes#24482, but we seem to be affected by that.
We need to confirm whether it’s the
kube proxy
that’s broken and we cannot do anything, or there is something we can do on our end to make it work.The text was updated successfully, but these errors were encountered: