Add support for admin ServerUpdate to update containers simultaneously

[harshavardhana]

No description provided.

[harshavardhana]

This PR testing would depend on the PR minio/minio#10107 here

[harshavardhana]

Tested all the changes are working as expected

diff --git a/examples/tenant.yaml b/examples/tenant.yaml
index 0abf379..254f440 100644
--- a/examples/tenant.yaml
+++ b/examples/tenant.yaml
@@ -42,7 +42,8 @@ spec:
       prometheus.io/port: "9000"
       prometheus.io/scrape: "true"
   ## Registry location and Tag to download MinIO Server image
-  image: minio/minio:RELEASE.2020-07-22T00-26-33Z
+  image: y4m4/minio:RELEASE.2020-07-21T01-08-20Z
+  #image: minio/minio:RELEASE.2020-07-22T00-26-33Z
   ## A ClusterIP Service will be created with the given name
   serviceName: minio-internal-service
   zones:
@@ -56,7 +57,8 @@ spec:
             - ReadWriteOnce
           resources:
             requests:
-              storage: 1Ti
+              storage: 20Gi
+          storageClassName: direct.csi.min.io
   ## Mount path where PV will be mounted inside container(s). Defaults to "/export".
   mountPath: /export
   ## Sub path inside Mount path where MinIO starts. Defaults to "".
diff --git a/minio-operator.yaml b/minio-operator.yaml
index 58617d6..7dd915c 100644
--- a/minio-operator.yaml
+++ b/minio-operator.yaml
@@ -276,7 +276,7 @@ spec:
         name: minio-operator
     spec:
       containers:
-        - image: minio/k8s-operator:3.0.0
-          imagePullPolicy: IfNotPresent
+        - image: y4m4/k8s-operator:test
+          imagePullPolicy: Always
           name: minio-operator
       serviceAccountName: minio-operator

Apply the following diff locally and then change the container image after deployment
with a second kubectl apply -f you can see the container restart and update first
before they do rolling upgrades.

[nitisht]

LGTM & Tested