Upgrading GlusterFS

You can upgrade your GlusterFS cluster that was configured in IBM® Cloud Private Version 3.1.1.

Your GlusterFS cluster is automatically upgraded if you configured GlusterFS in IBM Cloud Private Version 3.1.1 in one of the following ways:

• You configured GlusterFS while you installed your IBM Cloud Private cluster.
• You used the add-on command to configure GlusterFS after you installed IBM Cloud Private.

In IBM Cloud Private Version 3.1.1 or Version 3.1.0, you configured GlusterFS by installing the Helm chart, complete these steps to upgrade the GlusterFS Helm chart to version 1.3.0 in IBM Cloud Private Version 3.1.2:

Note: IBM Cloud Private Version 3.1.0 uses GlusterFS Helm chart Version 1.1.0 and IBM Cloud Private Version 3.1.1 uses GlusterFS Helm chart Version 1.2.0. If you do not want to upgrade, you can continue to use the GlusterFS Helm chart Version 1.2.0 or 1.1.0, whichever is applicable, with IBM Cloud Private Version 3.1.2.

Before you begin, ensure that you set up the following CLIs:

• Helm CLI
• kubectl CLI

Complete these steps to upgrade GlusterFS:

1. Patch GlusterFS daemonset and Heketi deployment. Run these commands:

   1. Get the latest version of GlusterFS Helm chart that is installed.

      helm list --tls | grep gluster
      

      Following is a sample output:

      gfsissue                        1               Thu Jan 25 22:31:53 2019        DEPLOYED        ibm-glusterfs-1.2.0                      kube-system
      

   2. Get the GlusterFS daemonset.

      kubectl -n kube-system get daemonset -l glusterfs=daemonset
      

      Following is a sample output:

      NAME                           DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR         AGE
      gfsissue-glusterfs-daemonset   4         4         4         4            4           hostgroup=glusterfs   4m
      

   3. Patch the daemonset.

      kubectl -n kube-system patch daemonset gfsissue-glusterfs-daemonset  --type json  -p='[{"op": "remove", "path": "/spec/selector/matchLabels/version"}]'
      

      Following is a sample output:

      daemonset.extensions/gfsissue-glusterfs-daemonset patched
      

   4. Get information about Heketi deployment.

      kubectl -n kube-system get deployment -l glusterfs=heketi-deployment
      

      Following is a sample output:

      NAME                                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
      gfsissue-glusterfs-heketi-deployment   1         1         1            0           3m
      

   5. Patch Heketi deployment.

      kubectl -n kube-system patch deployment gfsissue-glusterfs-heketi-deployment --type json  -p='[{"op": "remove", "path": "/spec/selector/matchLabels/version"}]'
      

      Following is a sample output:

      deployment.extensions/gfsissue-glusterfs-heketi-deployment patched
      

2. Log on to the management console.

3. Locate the GlusterFS Helm chart.
4. Click Upgrade to upgrade the chart to Version 1.3.0.

Note: Zero downtime upgrade of GlusterFS cluster is not supported when you upgrade from IBM Cloud Private Version 3.1.1 to Version 3.1.2. While the GlusterFS pods are upgraded, GlusterFS volumes are not accessible to application pods until the GlusterFS pods are running.