Rolling Back a Container Gateway

Using Helm with Kubernetes, you can roll back the last installation of the Gateway cluster. When you roll back your Gateway cluster, you remove all policies, environment configurations, and other deployment dependencies from the initial installation.
This described procedure uses third-party Helm Commands. For the latest instructions and best practices for using Helm and Helm Charts, see Helm documentation.
Similar to the Kubernetes rolling updates strategy used for which allows for zero-downtime upgrades, you can execute a zero-downtime rollback as well for your Container Gateway cluster.
Recall the helm history output from our update example:
$ helm history gateway ... REVISION UPDATED STATUS CHART DESCRIPTION 1 Fri Sep 18 13:05:00 2020 SUPERCEDED apigateway-10.0 Install complete 2 Mon Sep 21 10:30:15 2020 SUPERCEDED apigateway-10.0 Install complete 3 Mon Sep 21 11:56:10 2020 DEPLOYED apigateway-10.0 Upgrade complete
Identify the revision number you'd like the Gateway cluster to roll back to. For example, if you want to roll back to revision 2, execute the following Helm command (replace the 'gateway' name with the name of the actual release name for your Gateway deployment):
$ helm rollback gateway 2
Check the history of your Gateway cluster again and you should see that revision 4 serves as a record to show that revision 3 has been superceded by a copy of revision 2:
REVISION UPDATED STATUS CHART DESCRIPTION 1 Fri Sep 18 13:05:00 2020 SUPERCEDED apigateway-10.0 Install complete 2 Mon Sep 21 10:30:15 2020 SUPERCEDED apigateway-10.0 Install complete 3 Mon Sep 21 11:56:10 2020 SUPERCEDED apigateway-10.0 Upgrade complete 4 Mon Sep 21 13:00:00 2020 SUPERCEDED apigateway-10.0 Rollback to 2