<p><strong>When the client tries to connect our ingress defined endpoint via a <code>wss://</code> request, the app returns 400 bad request, which according to socket.io docs is due to missing headers removed by load balancing proxies like nginx.</strong> </p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: my-ingress
  annotations:
    nginx.org/websocket-services: service-name
spec:
  tls:
    - hosts:
        - www.myhost.com
  rules:
    - host: www.myhost.com
      http:
        paths:
          - path: /
            backend:
              serviceName: service-name
              servicePort: 80
</code></pre>

<p>From the logs in the IBM provided ingress controller it seems to be a fork of this <a href="https://github.com/nginxinc/kubernetes-ingress" rel="noreferrer">nginx ingress controller</a>. Which says that the annotation <code>nginx.org/websocket-services</code> adds support for websockets by adding directives to the generated nginx conf to pass the required headers. We have tried this as per above but to no avail. </p>

<p>Has anyone had any success making this annotation work? 
Any workarounds for adding to the generated nginx conf? </p>

<p>Any IBM people know if this functionality was intentionally removed from the fork? And if there is any way to add support for websockets in the IBM version of Kubernetes? </p>

<p>Websockets is not currently supported, we are working on adding it and I will update here when it is available.</p>

<p>Thank you</p>

<p>Edit: Websocket support is available in all regions, the annotation for it is:</p>

<pre><code>  annotations:
    ingress.bluemix.net/websocket-services: service-name
</code></pre>
