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

kubectl proxy appears to break WebSockets #1427

Closed
errordeveloper opened this issue May 4, 2016 · 7 comments
Closed

kubectl proxy appears to break WebSockets #1427

errordeveloper opened this issue May 4, 2016 · 7 comments
Labels
bug Broken end user or developer functionality; not working as the developers intended it k8s Pertains to integration with Kubernetes

Comments

@errordeveloper
Copy link
Contributor

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.

@errordeveloper errordeveloper added the k8s Pertains to integration with Kubernetes label May 4, 2016
@errordeveloper
Copy link
Contributor Author

errordeveloper commented May 4, 2016

To reproduce, do this follow K8s Anywhere setup and deploy scope like this:

kubectl create -f https://gist.github.com/errordeveloper/9d9a995df05064ea3f600a0378de3aaf/raw/scope.json --validate=false

You should be able to access the app on the following URL and observe error 400 occurring for all of WebSocket requests.

http://localhost:8001/api/v1/proxy/namespaces/default/services/weavescope-app:app/

@errordeveloper errordeveloper added this to the 0.15.0 milestone May 4, 2016
@errordeveloper
Copy link
Contributor Author

errordeveloper commented May 4, 2016

xref kubernetes/kubernetes#25126

@errordeveloper
Copy link
Contributor Author

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

@errordeveloper errordeveloper removed this from the 0.15.0 milestone May 4, 2016
@2opremio
Copy link
Contributor

2opremio commented May 4, 2016

I think there's little point in keeping this issue open when there's an upstream ticket already tracking it.

@errordeveloper
Copy link
Contributor Author

That's true, I created this in the process of figuring it out. However, if
we close it now, we should consider that it's referenced in Kubernetes
repo, closing it would indicate as if it's no longer a problem for us,
while still really is a problem.

On Wed, 4 May 2016, 15:53 Alfonso Acosta, notifications@github.com wrote:

I think there's little point on keeping this issue open when there's an
upstream ticket already tracking it.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1427 (comment)

@rade rade added the bug Broken end user or developer functionality; not working as the developers intended it label Jul 4, 2016
@satyamz
Copy link
Contributor

satyamz commented Feb 15, 2018

Hi all, I am getting the same problem. I am not able to access the weave-scope live mode (communicates using web sockets). However, I am able to access pause mode (Plain http).
I am trying to access weave-scope using /api/v1/namespaces/weave/services/weave-scope-app/proxy/

Is this issue resolved yet? If not, then please provide me some pointers so that I can try to work on it.

@errordeveloper
Copy link
Contributor Author

@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 kubectl port-foward (as describe in the docs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it k8s Pertains to integration with Kubernetes
Projects
None yet
Development

No branches or pull requests

4 participants