Universal Contact Service Release Notes
From Genesys Documentation
This topic is part of the manual Genesys Engage Cloud Release Notes for version Current of Genesys Engage Multicloud Release Notes.
Contents
Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.
Related documentation:
| Released on | Released for | Highlights |
|---|---|---|
| September 10, 2021 |  |
Support for arbitrary UIDs in private edition deployments on OpenShift. |
| June 30, 2021 | |
Early Adopter Program support for Genesys Engage cloud private edition. |
September 10, 2021
Private edition: 100.0.093.0015 available September 10, 2021For private edition
- UCS now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
- The Dockerfile has been modified to specify container and file ownership as user=500 (genesys) and group=0 (root).
- The podSecurityContext settings exposed in the default values.yaml file specify the user and group IDs for the genesys user (500:500:500). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs.
- UCS is deployed using ServiceAccounts that use the restricted Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom genesys-restricted SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the genesys-restricted SCC has been deprecated. If you previously deployed <service> using the genesys-restricted SCC, Genesys recommends that you redeploy <service> so that you use arbitrary UIDs. (UCSX-2349)
More info: OpenShift security settings
June 30, 2021
Private edition: 9.5.000.87 available June 30, 2021For private edition
- Starting with this release, Universal Contact Service is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (UCSX-2020)