How to upgrade Operator and Tenant when using ArgoCD - cniackz/public GitHub Wiki

Objective:

To show how to upgrade Operator and Tenant when using ArgoCD

Pre-Steps:

Have a cluster ready and deployed with Operator and Tenant installed via ArgoCD as shown in our wiki or similar: ArgoCD with MinIO Example

Steps to Upgrade Operator:

Edit in your Git Repository the Operator Helm Chart by looking at our Supported Charts in https://github.com/minio/operator/tree/master/helm-releases or point your App to use new path for the chart with the objective of having new values defined in your Git Repo for your App.

In this example I just changed the PATH from minio-operator to minio-operator-5-0-9 where my repo is located at: https://github.com/cniackz/minio-argocd

Then Synch the changes and new Operator will be in place:

Operator is now in 5.0.9:

$ k get pods minio-operator-5df446dcc5-frlxt -n minio-operator -o yaml | k neat > operator-pod.yaml

$ yq '.spec.containers[0].image' operator-pod.yaml 
quay.io/minio/operator:v5.0.9

Steps to Upgrade Tenant:

Similarly update the Tenant in your ArgoCD App by editing the values in your Helm Chart of your repo or pointing to a new one.

In this example, I changed from minio-tenant to minio-tenant-5-0-9 in my personal repo: https://github.com/cniackz/minio-argocd

Then Sync changes.
Now sts and minio pods are using the image quay.io/minio/minio:RELEASE.2023-09-07T02-05-02Z defined in the latest chart we provided.

$ k get pod myminio-pool-0-0 -n minio-tenant -o yaml | k neat > minio-pod.yaml

$ yq '.spec.containers[0].image' minio-pod.yaml 
quay.io/minio/minio:RELEASE.2023-09-07T02-05-02Z

Verify Tenant is still healthy:

$ k get tenant -n minio-tenant
NAME      STATE         AGE
myminio   Initialized   35m

$ k get tenant -n minio-tenant -o yaml > tenant.yaml

$ yq '.items[0].status' tenant.yaml 
availableReplicas: 4
certificates:
  autoCertEnabled: true
  customCertificates: {}
currentState: Initialized
drivesOnline: 16
healthStatus: green
pools:
  - legacySecurityContext: false
    ssName: myminio-pool-0
    state: PoolInitialized
provisionedBuckets: true
revision: 0
syncVersion: ""
usage:
  rawCapacity: 171798691840
  rawUsage: 689775116288
writeQuorum: 12