how to proxy websocket with kong ingress

[w564791]

likes use nginx:

proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";

what should i do

[rainest]

Did you encounter any issues when trying to do this? WebSocket proxying is supported by default and doesn't require any special configuration: if you send a WebSocket Upgrade request from your client to any route, we'll proxy it upstream, return the upstream 101 response, and continue proxying the WebSocket traffic after.

[w564791]

It support ws:// protocol ，not support http://. Protocol upgrade to websocket 发自我的iPhone 在 2021年1月6日，上午5:14，Travis Raines <[email protected]> 写道：  Did you encounter any issues when trying to do this? WebSocket proxying is supported by default<https://docs.konghq.com/2.2.x/proxy/#proxy-websocket-traffic> and doesn't require any special configuration: if you send a WebSocket Upgrade request from your client to any route, we'll proxy it upstream, return the upstream 101 response, and continue proxying the WebSocket traffic after. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#995 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD2VN52VQGLGT2YEGSR6TI3SYN6LRANCNFSM4VNY4HQQ>.

[rainest]

Can you show an example of what you're seeing? Sending an initial https://-scheme request with an Upgrade header should be fine.

[rainest]

Closing this due to inactivity. Feel free to respond back and we can reopen this if needed.

[priyanka-raghavan-maersk]

Hi do you have an example of how you got it work?

[priyankaraghavan]

It is working now unauthenticated.

[Gowtham029]

@priyankaraghavan do you have an example of how you got it work.

[priyanka-raghavan-maersk]

Yes you can pass in your access token as a query param

wss://gateway-url/route-path/notification/notificationHub?access_token=<access_token>

Actually i did not have to do anything special with kong to make it work

[myvodx]

We need to update the ingress annotations as bellow.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  # ... other properties
  annotations:
    konghq.com/headers.Connection: "Upgrade"
    konghq.com/headers.Upgrade: "WebSocket"
   ...

See more information:

• https://docs.konghq.com/gateway-oss/2.2.x/proxy/#proxy-websocket-traffic
• https://docs.konghq.com/kubernetes-ingress-controller/latest/references/annotations/#konghqcomheaders

[aleksandarsavev]

Is there a full example of an Ingress configuration. I always receive 200 OK and it cannot continue the websocket handshake.