Upgrade, roll back, or uninstall Genesys Engagement Service
Contents
Learn how to upgrade, roll back, or uninstall Genesys Engagement Service.
Supported upgrade strategies
Genesys Callback supports the following upgrade strategies:
| Service | Upgrade Strategy | Notes |
|---|---|---|
| Genesys Engagement Service | Rolling Update |
For a conceptual overview of the upgrade strategies, refer to Upgrade strategies in the Setting up Genesys Multicloud CX Private Edition guide.
| Versions must match | Ensure that the version of GES and the Helm chart match. While Helm charts might work with other versions of GES, this is not tested and Genesys cannot guarantee success. |
Provided there are no issues or errors when running the Helm command, you can expect GES to work with any updates supplied in the latest version of the Helm charts. However, in some instances, there might be changes to the GES Helm manifest that, due to restrictions in Kubernetes, require the existing GES deployment to be uninstalled and then re-installed, rather than simply upgraded in place. Consult the Callback Release Notes to see if this will be necessary.
Timing
A regular upgrade schedule is necessary to fit within the Genesys policy of supporting N-2 releases, but a particular release might warrant an earlier upgrade (for example, because of a critical security fix).
If the service you are upgrading requires a later version of any third-party services, upgrade the third-party service(s) before you upgrade the private edition service. For the latest supported versions of third-party services, see the Software requirements page in the suite-level guide.
Scheduling considerations
Genesys recommends that you upgrade the services methodically and sequentially: Complete the upgrade for one service and verify that it upgraded successfully before proceeding to upgrade the next service. If necessary, roll back the upgrade and verify successful rollback.
Upgrade the Helm deployment for GES during a prescribed maintenance window.
Monitoring
Monitor the upgrade process using standard Kubernetes and Helm metrics, as well as service-specific metrics that can identify failure or successful completion of the upgrade (see Observability in Genesys Callback).
Genesys recommends that you create custom alerts for key indicators of failure — for example, an alert that a pod is in pending state for longer than a timeout suitable for your environment. Consider including an alert for the absence of metrics, which is a situation that can occur if the Docker image is not available. Note that Genesys does not provide support for custom alerts that you create in your environment.
Preparatory steps
Ensure that your processes have been set up to enable easy rollback in case an upgrade leads to compatibility or other issues.
Each time you upgrade a service:
- Review the release note to identify changes.
- Ensure that the new package is available for you to deploy in your environment.
- Ensure that your existing <override>-values.yaml file is available and update it if required to implement changes.
Rolling Update
Rolling Update: Upgrade
Execute the following command to upgrade <service>:
helm upgrade --install <service> -f <override>-values.yaml <Helm package> -n <namespace>Tip: If your review of Helm chart changes (see Preparatory Step 3) identifies that the only update you need to make to your existing <override>-values.yaml file is to update the image version, you can pass the image tag as an argument by using the --set flag in the command:
helm upgrade --install <service> -f <override>-values.yaml <Helm package> --set <service>.image.tag=<new service version>Example
> helm upgrade --install -n <GES_NAMESPACE> -f <path/to/values.yaml> <GES_RELEASE_NAME> <PATH_TO_GES_HELM_CHART>
Rolling Update: Verify the upgrade
Follow usual Kubernetes best practices to verify that the new service version is deployed. See the information about initial deployment for additional functional validation that the service has upgraded successfully.
You can verify that GES has upgraded successfully by either looking at dashboards (if provisioned) or using the health check APIs for GES (through the internal port query ges:3050/ges/v1/health/detail) to make sure that all dependencies are working as provided.
Rolling Update: Rollback
Execute the following command to roll back the upgrade to the previous version:
helm rollback <service>or, to roll back to an even earlier version:
helm rollback <service> <revision version>Alternatively, you can re-install the previous package:
- Revert the image version in the <service>.image.tag parameter in the <override>-values.yaml file. If applicable, also revert any configuration changes you implemented for the new release.
- Execute the following command to roll back the upgrade:
helm upgrade --install <service> -f <override>-values.yaml <old Helm package>
- Tip: You can also directly pass the image tag as an argument by using the --set flag in the command:
helm upgrade --install <service> -f <override>-values.yaml <old Helm package> --set <service>.image.tag=<old service version>
Rolling Update: Verify the rollback
Verify the rollback in the same way that you verified the upgrade (see Rolling Update: Verify the upgrade).
Uninstall
Execute the following command to uninstall <service>:
helm uninstall <service> -n <namespace>Depending on how services like Postgres and Redis are provisioned for GES, you will have to decommission those services separately. Discussion of that process is outside the scope of this document.