scaling websocket apps with k8s

The application allows people to have video/audio calls.
and it uses a socket for streaming the data.

as the application is hosted in the k8s, when a pod dies due to any reason, the video call of those users whose connections were maintained in that specific pod disrupts and call disconnects.

as you might know, for each connection it allots a port in that machine.
due to this fact, I was just creating new pods and in the new k8s node. which would eventually have lots of ports available to use.

deep down, this is not something best solution I believe.
any advice on what are the best ways to scale such applications in k8s would be much appreciated.