operator helm upgrade from 4.5.8 to 5.0.3 - cniackz/public GitHub Wiki

  1. In a cluster, installed Operator version 4.5.8 with Helm:
helm install \
     --namespace minio-operator \
     --create-namespace \
     minio-operator ./operator-4.5.8.tgz
$ k get pods minio-operator-5bccb66546-6792k  -n minio-operator -o yaml | yq '.spec.containers[0].image'
minio/operator:v4.5.8
  1. Deployed a tenant with Helm:
helm install \
  --namespace tenant-ns \
  --create-namespace \
  tenant-ns ./tenant-4.5.8.tgz
$ k get pods -n tenant-ns
NAME              READY   STATUS    RESTARTS   AGE
minio1-pool-0-0   1/1     Running   0          108s
minio1-pool-0-1   1/1     Running   0          108s
minio1-pool-0-2   1/1     Running   0          108s
minio1-pool-0-3   1/1     Running   0          107s
  1. Put some Objects:
$ mc ls myminio/testing --insecure
[2023-04-13 15:28:26 EDT] 1.1MiB STANDARD Screenshot 2023-04-12 at 3.39.41 PM.png
  1. Upgraded Operator:
$ helm upgrade \
     --namespace minio-operator \
     minio-operator ./operator-5.0.3.tgz
  1. Restarted Operator Pods

  2. Waited some time for the upgrade to go thru.

  3. Get the Objects after Tenant initialized again:

$ mc ls myminio/testing --insecure
[2023-04-13 15:28:26 EDT] 1.1MiB STANDARD Screenshot 2023-04-12 at 3.39.41 PM.png
  1. Notice you have now two container per node, meaning sidecar is running:
$ k get pods -n tenant-ns
NAME              READY   STATUS    RESTARTS   AGE
minio1-pool-0-0   2/2     Running   0          3m25s
minio1-pool-0-1   2/2     Running   0          3m41s
minio1-pool-0-2   2/2     Running   0          3m47s
minio1-pool-0-3   2/2     Running   0          3m54s