Ben Hardill<p>For people with large WebSocket workloads using the ingress-nginx controller.</p><p>I recently hit this issue:</p><p><a href="https://github.com/kubernetes/ingress-nginx/issues/2461" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kubernetes/ingress-</span><span class="invisible">nginx/issues/2461</span></a></p><p>This drops all current WebSocket connections when ever the controller reloads the config. This can be triggered by adding/removing a new Ingress object (which this project does regularly due to customer load).</p><p>We ended up moving the WebSocket ingress to a separate LoadBalancer/Ingress class.</p><p><a href="https://bluetoot.hardill.me.uk/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kubernetes</span></a> <a href="https://bluetoot.hardill.me.uk/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nginx</span></a> <a href="https://bluetoot.hardill.me.uk/tags/websockets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>websockets</span></a></p>