Is it possible to configure the rolling deployment in k8s to spin up all new pods before the “old” pods are deleted?

Background:
We have long living TCP connections distributed over 2 pods. When a pod is deleted and therefore the tcp connection closed, the tcp clients try to reconnect immediately.
So after a deployment all tcp connections are established on the pod which was updated first, instead of distributed evenly.