19. Upgrading Robin Cloud Native Storage¶
You can upgrade your Robin Cloud Native Storage (CNS) cluster from your current version to a later CNS version. After you upgrade your cluster, you can use the latest Robin CNS features.
This section describes the steps to upgrade the Robin CNS cluster.
19.1. Pre Robin Upgrade Checklist¶
All nodes within the Kubernetes cluster must be in the healthy state.
Make sure that no control plane operations, including those associated with applications and volumes, are performed by any user(s) until the entire upgrade process is completed.
19.2. Upgrade using Robin installer¶
You can upgrade your Robin CNS cluster using the Robin installer. You must run the Robin installer command on the node from which you can access the CNS cluster using the kubectl command.
19.2.1. Upgrade on Google GKE¶
You can upgrade your Robin CNS cluster installed on Google GKE.
Complete the following steps to upgrade the Robin CNS cluster on Google GKE:
Note
If you have already downloaded the Robin installation tar file, proceed to step 7.
Access the get.robin.io website.
In the DOWNLOAD FOR FREE box, enter your business email address and click Sign in to Download.
Check the email ID you provided for the passwordless login link and click the link.
After logging in to the get.robin.io website, hover over to the Deploy on Google GKE/Anthos box and click Download and Install.
In the Deploy on Google GKE/Anthos window, copy either the
wget
orcurl
command.Access your Robin CNS cluster and run the copied command on the node from which you can access your cluster using the kubectl command to download the installation tar file:
$ wget "http://get.robin.io/download/storage?id=<USERID>&type=gke" -O robin-install.tar
After downloading the installation tar file, run the following command to untar the contents into a new directory:
$ mkdir -p ./robin-upgrade && tar -xf robin-install.tar -C ./robin-upgrade
Run the following command to make the newly created directory your current working directory:
$ cd robin-upgrade
Run the following command to upgrade Robin CNS:
$ ./install-robin.sh --version=<version number> --upgrade --cluster-name=<cluster_name> --zone-name=<zone_name>
Example
$ ./install-robin.sh --version=5.3.14-72 --upgrade --cluster-name=nightly-cluster --zone-name=us-central1 Validating Kubernetes cluster......Done Validating kubernetes cluster permissions......Done Validating robin cluster yaml......Done Installing Robin operator...........Done Upgrading Robin Operator to version 5.3.14-72 ......Done Upgrading Robin CR from version 5.3.8-595 to 5.3.14-72 .........Done Upgrading Robin cluster......Done
19.2.2. Upgrade on Google Anthos¶
You can upgrade your Robin CNS cluster installed on Google Anthos.
Complete the following steps to upgrade the Robin CNS cluster on Google Anthos:
Note
If you have already downloaded the Robin installation tar file, proceed to step 7.
Access the get.robin.io website.
In the DOWNLOAD FOR FREE box, enter your business email address and click Sign in to Download.
Check the email ID you provided for the passwordless login link and click the link.
After logging in to the get.robin.io website, hover over to the Deploy on Google GKE/Anthos box and click Download and Install.
In the Deploy on Google GKE/Anthos window, copy either the
wget
orcurl
command.Access your Robin CNS cluster and run the copied command on the node from which you can access your cluster using the kubectl command to download the installation tar file:
$ wget "http://get.robin.io/download/storage?id=<USERID>&type=gke" -O robin-install.tar
After downloading the installation tar file, run the following command to untar the contents into a new directory:
$ mkdir -p ./robin-upgrade && tar -xf robin-install.tar -C ./robin-upgrade
Run the following command to make the newly created directory your current working directory:
$ cd robin-upgrade
Run the following command to upgrade Robin CNS:
$ ./install-robin.sh --version=<version number> --upgrade
Example
$ ./install-robin.sh --version=5.3.14-72 --upgrade Validating Kubernetes cluster......Done Validating kubernetes cluster permissions......Done Validating robin cluster yaml......Done Installing Robin operator...........Done Upgrading Robin Operator to version 5.3.14-72 ......Done Upgrading Robin CR from version 5.3.8-595 to 5.3.14-72 .........Done Upgrading Robin cluster......Done
19.3. Manual Upgrade Steps¶
When upgrading to Robin CNS, if Zalando Postgres operator is already installed on your cluster, you must skip the Postgres operator installation as part of the Robin CNS upgrade.
To skip Postgres operator installation, you must use the skip_postgres_operator
option as part of the Robin cluster CR YAML file. If the value of the option is set to 1
, Robin CNS upgrade operation skips the Postgres operator installation.
By default, the option is set to 0
enabling the installation of the Zalando Postgres operator.
Complete the following steps to upgrade to the latest Robin CNS version:
Untar the Robin CNS folder.
Run the
cd
command to access the folder where you untarred the Robin CNS binaries.Run the following command to generate the
robin-operator
and Robin CR YAML files.# ./install-robin.sh -g --image-registry-path="gcr.io/robinio-public/robin-storage"
Apply the
robin-operator
YAML file by running the following command.kubectl apply -f ./robin-operator.yaml.tmp
Note
Wait for the Robin operator Pod to come up.
Run the following command to wait for the robin-operator Pod to come up with the new Robin CNS version.
# kubectl rollout status -n robinio deploy/robin-operator
Run the following command to update the RobinCluster Custom Resource.
# kubectl edit robincluster -n robinio
Change the
image_robin
andimage_ubbagent
to point to the latest Robin CNS version:spec: image_robin: robinsys/robinimg:5.4.8-313 image_ubbagent: robinsys/ubbagent:5.4.8-ent-1 image_puller: robinsys/robin-image-puller:v1 image_nfs_server: robinsys/nfs-server:v1
After running the above command and making changes, Pods in the robinio
namespace will be redeployed with the new version.
19.3.1. Upgrade Verification¶
Perform the following steps to verify that the upgrade is complete:
Run the following command to make sure that all the images are properly upgraded to the latest image:
# kubectl get pods -n robinio -o=custom-columns=PODNAME:.metadata.name,IMAGE:.spec.containers[*].image
Run the following command to check the progress of the upgrade:
# kubectl rollout status -n robinio ds/robin-worker
Log in to the Master Pod and run the following command to verify that all the hosts are displaying the Robin CNS v5.4.8 version and are in the
Ready
status:# robin host list
Example
[robin ~]# robin host list Id | Hostname | Version | Status | RPool | Avail. Zone | LastOpr | Roles | Isol Shared Cores | Isol Dedicated Cores | Non-Isol Cores | GPUs | Mem | HDD(#/Alloc/Total) | SSD(#/Alloc/Total) | Pod Usage | Joined Time -------------+-------------------------------+---------- +--------+---------+-------------+---------+-------+-------------------+----------------------+----------------+-------+---------------+--------------------+--------------------+-----------+---------------------- 1694024781:1 | sms210p-01.robinsystems.com | 5.4.8-313 | Ready | default | N/A | ONLINE | S | 0/0/0 | 0/0/0 | 637/3/640 | 0/0/0 | 101G/23G/125G | -/-/- | 2/55G/476G | 80/30/110 | 06 Sep 2023 04:27:17 1694024781:2 | sms201p-02.robinsystems.com | 5.4.8-313 | Ready | default | N/A | ONLINE | S | 0/0/0 | 0/0/0 | 634/6/640 | 0/0/0 | 104G/20G/125G | -/-/- | 2/55G/476G | 74/36/110 | 06 Sep 2023 04:27:19 1694024781:3 | sms210p-03.robinsystems.com | 5.4.8-313 | Ready | default | N/A | ONLINE | S | 0/0/0 | 0/0/0 | 633/7/640 | 0/0/0 | 103G/21G/125G | -/-/- | 2/55G/476G | 53/57/110 | 06 Sep 2023 04:27:20 * Note: all values indicated above in the format XX/XX/XX represent the Free/Allocated/Total values of the respective resource unless otherwise specified. In addition allocated values for compute resource such as cpu, memory and pod usage includes reserved values for the corresponding resource.
Note
After upgrading to Robin CNS v5.4.8, if you are using a robin client outside Robin Pods, you must upgrade to the latest version of the Robin CLI Client.