install: add rollingUpdate strategy in caa daemonset

[huoqifeng]

Fixes: #1214

[huoqifeng]

I'm verifying the change following this steps:

• Installed an IKS cluster with 2 nodes
• Labled the nodes via command kubectl label nodes --all node.kubernetes.io/worker=
• Deploy PeerPod via commands after fill correct fields in install/overlays/ibmcloud/kustomization.yaml

kubectl apply -k "github.com/confidential-containers/operator/config/default?ref=v0.7.0"
kubectl apply -k "github.com/confidential-containers/operator/config/samples/ccruntime/peer-pods?ref=v0.7.0"
kubectl apply -k install/overlays/ibmcloud

• Checked the rolling update strategy added as below via command kubectl -n confidential-containers-system get daemonset cloud-api-adaptor-daemonset -o yaml

  updateStrategy:
    rollingUpdate:
      maxSurge: 0
      maxUnavailable: 1
    type: RollingUpdate

• Changed the image latest tag to another tag in image: quay.io/confidential-containers/cloud-api-adaptor:latest via command kubectl -n confidential-containers-system edit daemonset cloud-api-adaptor-daemonset
• Watch the daemonset status via command kubectl -n confidential-containers-system get po --watch |grep cloud-api-adaptor-daemonset

# kubectl -n confidential-containers-system get po --watch |grep cloud-api-adaptor-daemonset
cloud-api-adaptor-daemonset-jskdb                 1/1     Running   0          2m59s
cloud-api-adaptor-daemonset-n5m79                 1/1     Running   0          2m57s
cloud-api-adaptor-daemonset-jskdb                 1/1     Terminating   0          3m20s
cloud-api-adaptor-daemonset-jskdb                 0/1     Terminating   0          3m21s
cloud-api-adaptor-daemonset-jskdb                 0/1     Terminating   0          3m21s
cloud-api-adaptor-daemonset-jskdb                 0/1     Terminating   0          3m21s
cloud-api-adaptor-daemonset-2sz5q                 0/1     Pending       0          0s
cloud-api-adaptor-daemonset-2sz5q                 0/1     Pending       0          0s
cloud-api-adaptor-daemonset-2sz5q                 0/1     ContainerCreating   0          0s
cloud-api-adaptor-daemonset-2sz5q                 1/1     Running             0          2s
cloud-api-adaptor-daemonset-n5m79                 1/1     Terminating         0          3m21s
cloud-api-adaptor-daemonset-n5m79                 0/1     Terminating         0          3m22s
cloud-api-adaptor-daemonset-n5m79                 0/1     Terminating         0          3m22s
cloud-api-adaptor-daemonset-n5m79                 0/1     Terminating         0          3m22s
cloud-api-adaptor-daemonset-xbtjr                 0/1     Pending             0          0s
cloud-api-adaptor-daemonset-xbtjr                 0/1     Pending             0          0s
cloud-api-adaptor-daemonset-xbtjr                 0/1     ContainerCreating   0          0s
cloud-api-adaptor-daemonset-xbtjr                 1/1     Running             0          2s

We can see the pod cloud-api-adaptor-daemonset-xbtjr was created after pod cloud-api-adaptor-daemonset-2sz5q running completely.

[tumberino]

lgtm

[bpradipt]

/lgtm