I have installed Kong as ingress controller in Kubernetes to expose microservices.
There is 1 specific microservice, which uses websockets and this is the one that is giving me problems. Kong is rejecting websocket connections for some reason, I have installed the cors plugin, but I still can’t establish the connection.
In local the service works perfect, I can connect without problems. But when I upload it to production and put it behind Kong, when accessing the necessary route for the connection to the websocket, it rejects the connection and does not reach the service pod. While if I use one of the http endpoints of the same service, they work perfect, I only have problems with the websocket.
What problem may be happening in my case? I’ve been trying to fix it for a while but I don’t find much information.
What is the error you receive from Kong?
If you disabled the CORS plugin, does it work?
Iam trying to find any logs for the error. But i cant found anything.
I follow logs of proxy pod with this:
kubectl -n kong logs -f --tail=10 pod/ingress-kong-9994d9749-tpwkr proxy
but dont say anything about the requests.
this is the output:
Where i can find more Kong logs to see the request info?
Also i disabled the CORS plugin, but its still wrong.
Can you use Kong 1.3.1 and test this?
You might be running into https://github.com/Kong/kong/issues/5465.
Can anyone share an example of using websockets with kubernetes ingress controller (just the rough idea, i just need a starting place)? There is no mention of websocket in the kubernetes-ingress-controller/docs