Multiple pod restarts as part of operator updates that include webhooks

A new v7.2 operator pod starts and goes into creating
A New v7.2 webhook appears which contains the same caBundle value as the v7.1 wehbook
At this point requests are still going to the old v7.1 operator pod and working

New v7.2 operator pod becomes ready
Old v7.1 oprator is terminated
Old 7.1 webhook is deleted
At this point requests are going to the new v7.2 operator pod and working

Within a few seconds the following occurs (all within a ms of each other so we don't know cause vs effect)

A second new v7.2 operator pod is created. Looking at the deployment it appears this gets created because the pod spec olmcahash has been udpated
The ibm-appconnect-operator-service-cert secret updated
The v7.2 webhook updated with a new caBundle value
At this point all requests fail. We suspect this is because Kube is because all the requests are now made using the new caBundle, but they are hitting the original v7.2 pod which still has the old caBundle thus it fails. 

there is a window where requests fail i.e. its not a blue/green upgrade.

Request should not fail and there should not any impact while upgrading

https://issues.redhat.com/browse/RFE-3796