Recommendations in creating namespaces for Genesys Engage services deployment.
Namespaces for Genesys Engage services
A namespace provides a virtual cluster for applying access control policies and setting the scope of named resources such as internal DNS names, pods, services, deployments, and constraints for resource quotas.
For deploying Genesys Engage services, Genesys requires you to create a namespace per service group and deploy the associated services within that namespace.
Create the namespaces using the naming conventions given in the following table and defined in the Helm charts of the respective services. Note that most of the service groups contain several microservices.
The naming conventions meet Kubernetes requirements that the names of namespaces within a cluster must be unique. Note that, as described under Kubernetes clusters, you must use separate Kubernetes clusters if you want to deploy private edition instances in separate environments for testing, staging, production, and so on.
For more information, refer to the service guides of the individual services you are deploying.
|Genesys Web Services (GWS/GAPI)||gws|
|Genesys Engagement Service (Callback and Mobile)||ges|
|Historical Reporting Back-end (GIM)||gim,gca,gsp|
|Historical Reporting Front-end (GCXI)||gcxi|
|Digital-Legacy (Ixn Server)||ixn|
|IWD||iwd - plus 2 additional namespaces - iwddm, iwdem|
|Voice Legacy (Config, Stat Server, URS, OCS)||voice|
|WFM 3rd party Connector||gluswfm|
|Genesys Authentication services||gauth|
Namespace for third-party services
You can create a different namespace for installing the backend infrastructure services like Redis, PostgreSQL, etc. as long as the Genesys Engage service deployments have the required network access and the services have resolvable DNS names. The best way to manage your backend infrastructure services and Genesys Engage services is to decouple and deploy them in different clusters.