Change deployment strategy on test manifests (#1985)

We see a rare flake where our registry test deployment is using a different cert
to what we saved in a CM in our cluster.
As an attempt to mitigate, lets ensure that during rollout old pods are first gone, and only then new ones are introduced.

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>

manifests/templates/bad-webserver.yaml.in

@@ -7,6 +7,8 @@ metadata:
   labels:
     cdi.kubevirt.io/testing: ""
 spec:
+  strategy:
+    type: Recreate
   selector:
     matchLabels:
       name: cdi-bad-webserver

manifests/templates/file-host.yaml.in

@@ -7,6 +7,8 @@ metadata:
   labels:
     cdi.kubevirt.io/testing: ""
 spec:
+  strategy:
+    type: Recreate
   selector:
     matchLabels:
       name: cdi-file-host

manifests/templates/imageio.yaml.in

@@ -7,6 +7,8 @@ metadata:
   labels:
     cdi.kubevirt.io/testing: ""
 spec:
+  strategy:
+    type: Recreate
   replicas: 1
   selector:
     matchLabels:

manifests/templates/registry-host.yaml.in

@@ -6,6 +6,8 @@ metadata:
   labels:
     cdi.kubevirt.io/testing: ""
 spec:
+  strategy:
+    type: Recreate
   selector:
     matchLabels:
       name: cdi-docker-registry-host

manifests/templates/test-proxy.yaml.in

@@ -7,6 +7,8 @@ metadata:
   labels:
     cdi.kubevirt.io/testing: ""
 spec:
+  strategy:
+    type: Recreate
   replicas: 1
   selector:
     matchLabels:

manifests/templates/vcenter.yaml.in

@@ -7,6 +7,8 @@ metadata:
   labels:
     cdi.kubevirt.io/testing: ""
 spec:
+  strategy:
+    type: Recreate
   selector:
     matchLabels:
       app: vcenter