You can revert to an earlier version of Event Streams under certain conditions.
Prerequisites
Rolling back your Event Streams 2019.4.1 installation to an earlier version is only supported in the following cases:
- You can only roll back from a newer Helm chart version to an older chart version.
- You can only roll back to Event Streams 2019.2.1 (Helm chart version 1.3.0). Rolling back to earlier chart versions is not supported.
- Rolling back to an earlier Event Streams version is only supported if you have not modified your settings after deployment.
Rolling back
Using the UI
- Log in to your IBM Cloud Private cluster management console as an administrator. For more information, see the IBM Cloud Private documentation.
- Click Workloads > Helm Releases from the navigation menu.
- Locate the release name of your installation in the Name column, and click More options > Rollback in the corresponding row.
- Select the chart version to roll back to (1.3.0).
- Click Rollback.
Using the CLI
- Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
cloudctl login -a https://<cluster-address>:<cluster-router-https-port>
Important: You must have the Cluster Administrator role to roll back a chart version. - Run the
helm history
command to view previous versions you can roll back to:
helm history <release-name>
Where<release-name>
is the name that identifies your Event Streams installation.
For example:
$ helm history event-streams REVISION UPDATED STATUS CHART DESCRIPTION 1 Mon Dec 17 14:27:12 2018 SUPERSEDED ibm-eventstreams-prod-1.1.0 Install complete 2 Wed Apr 10 16:49:29 2018 SUPERSEDED ibm-eventstreams-prod-1.2.0 Upgrade complete 3 Mon Jul 15 12:16:34 2019 SUPERSEDED ibm-eventstreams-prod-1.3.0 Upgrade complete 4 Wed Oct 23 16:16:34 2019 DEPLOYED ibm-eventstreams-prod-1.4.0 Upgrade complete
- Run the
helm rollback
command as follows:
helm rollback <release-name> <revision>
Where<release-name>
is the name that identifies your Event Streams installation, and<revision>
is a number from theREVISION
column that corresponds to the version you want to revert to, as displayed in the result of thehelm history
command.
For example:
helm rollback event-streams 3
Post-rollback tasks
Rolling back to version 2019.2.1 deletes the restProxyExternalPort
value from the release ConfigMap, which means you will not be able to access the UI or use the schema registry feature. Use the following kubectl patch
command to fix this issue.
- Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
cloudctl login -a https://<cluster-address>:<cluster-router-https-port>
- Retrieve the
restProxyExternalPort
value as follows:
kubectl get svc $(kubectl get svc -o jsonpath='{range .items[*]}{.metadata.name}{"\n"}{end}' | grep rest-proxy-external) -o jsonpath='{range .spec.ports[?(@.name=="admin-rest-https")]}{.nodePort}{"\n"}{end}'
-
Run the following command:
kubectl patch configmap <release-name>-ibm-es-release-cm -n <namespace> --type='json' -p='[{"op": "add", "path": "/data/restProxyExternalPort", "value": "<restProxyExternalPort>"}]'
Where:
<release-name>
is the name that identifies your Event Streams installation.<namespace>
is the location of your installation.<restProxyExternalPort>
is the port you retrieved in the previous step.