Google Cloud: Rolling back a deployment

Rolling back

If you find that there is an issue with a cluster and you cannot fix it by updating the main branch and creating a new release, you can also rollback to a previous release.

The first thing to do is activate the correct cluster:

gcloud config configurations activate ubiquityrepo-us; gcloud container clusters get-credentials cluster-us --zone us-central1-a;

Next, get a list of builds from the helm chart:

helm history hyku 

You will be presented a list of the releases that have been deployed to that cluster:

REVISION        UPDATED                         STATUS          CHART           APP VERSION     DESCRIPTION
131             Mon Dec 20 09:40:33 2021        superseded      hyku-4.0.1      2.1.0-385       Upgrade complete
132             Mon Dec 20 15:03:02 2021        superseded      hyku-4.0.1      2.1.0-386       Upgrade complete
133             Wed Jan  5 10:17:35 2022        superseded      hyku-4.0.1      2.1.0-387       Upgrade complete
134             Thu Jan  6 13:45:49 2022        superseded      hyku-4.0.1      2.1.0-387       Rollback to 133
135             Thu Jan  6 13:49:08 2022        superseded      hyku-4.0.1      2.1.0-387       Rollback to 133
136             Fri Jan  7 09:43:39 2022        superseded      hyku-4.0.1      2.1.0-387       Rollback to 133
137             Tue Jan 25 09:59:59 2022        superseded      hyku-4.0.1      2.1.0-397       Upgrade complete
138             Fri Feb  4 21:20:28 2022        superseded      hyku-4.0.1      2.1.0-406       Upgrade complete
139             Wed Feb  9 16:23:10 2022        superseded      hyku-4.0.1      2.1.0-410       Upgrade complete
140             Thu Feb 24 10:04:31 2022        deployed        hyku-4.0.1      2.1.0-416       Upgrade complete

As you can see from the table above, the "APP VERSION" does not run sequentially. This is because only releases that are deployed to this cluster are listed.

To start the process of rolling back to a previous release you would use the following:

# helm rollback [release_name] [REVISION]

So if you wanted to rollback from revision 2.1.0-416 to 2.1.0-410, you would enter the following:

helm rollback hyku 139

You should then see Rollback was a success! Happy Helming!