Provide an update strategy to allow application updates

Default chart behavior with anti-affinity policies set leave pods in a
Pending state after an application update. Setting a RollingUpdate
strategy allows the new application version to be applied.

Change-Id: I0d3a84708283a198ef9534ca99f69453f56e01bb
Partial-Bug: #1876328
Signed-off-by: Robert Church <robert.church@windriver.com>

stx-cert-manager-helm/stx-cert-manager-helm/manifests/certmanager-manifest.yaml

@@ -70,6 +70,11 @@ data:
               values:
               - cert-manager
           topologyKey: kubernetes.io/hostname
+    strategy:
+      type: RollingUpdate
+      rollingUpdate:
+        maxSurge: 1
+        maxUnavailable: 1
     webhook:
       replicaCount: 1
       serviceName: "cm-cert-manager-webhook"
@@ -88,6 +93,11 @@ data:
                 values:
                 - webhook
             topologyKey: kubernetes.io/hostname
+      strategy:
+        type: RollingUpdate
+        rollingUpdate:
+          maxSurge: 1
+          maxUnavailable: 1
     cainjector:
       replicaCount: 1
       image:
@@ -105,6 +115,11 @@ data:
                 values:
                 - cainjector
             topologyKey: kubernetes.io/hostname
+      strategy:
+        type: RollingUpdate
+        rollingUpdate:
+          maxSurge: 1
+          maxUnavailable: 1
     acmesolver:
       image:
         repository: quay.io/jetstack/cert-manager-acmesolver