istio: Injecting sidecar breaks websocket connection
Deploying Node-red on k8s and exposing through ingress works fine until I modify my deployment to inject istio sidecar.
kubectl describe ing
–>
Name: hello-nodered
Namespace: default
Address:
Default backend: default-http-backend:80 (11.1.25.132:8080)
Rules:
Host Path Backends
---- ---- --------
*
/hello hello-nodered:1880 (<none>)
Annotations:
websocket-services: hello-nodered
enable-cors: true
rewrite-target: /
ssl-redirect: false
No events.
Now, if I do
kubectl get deployment/hello-nodered -o yaml | istioctl kube-inject -f - | kubectl apply -f -
the websocket connection from the editor does not work anymore:
I tried both ingress annotations kubernetes.io/ingress.class: "istio"
and kubernetes.io/ingress.class: "nginx"
, but always same issue. So I really suspect this is caused by the injected sidecar proxy.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 19 (8 by maintainers)
Commits related to this issue
- Merge release-1.1 to master (#840) * Doc fixes. * Add high-level overview and diagrams for MCP (#805) * document MCP * add additional note on NACK behavior * add a note about ignoring sta... — committed to thedemodrive/istio by ozevren 5 years ago
- Merge release-1.1 into master (#872) * Doc fixes. * Add high-level overview and diagrams for MCP (#805) * document MCP * add additional note on NACK behavior * add a note about ignoring stale... — committed to thedemodrive/istio by howardjohn 5 years ago
@rshriram Is there any other information I can collect to help figure this out?