Prevent active kubernetes pod from terminating

Question

We have a pod which serves HTTP traffic. When we update the image version of the parent deployment is there a way to prevent the pod from terminating until all current connections have finished?

We are not looking to inject an arbitrary delay but rather to intelligently monitor current client connections during the rolling update phase to ensure they are not terminated prematurely.