Describes the network settings required for Kubernetes clusters in Genesys Engage cloud private edition. For more information about networking outside Kubernetes clusters, see Networking overview.
Enabling Container Networking Interface
In your Kubernetes cluster, enable Container Networking Interface (CNI) or its equivalent to establish communication between pods in the cluster. In OpenShift environments, you must enable OpenShift Service-Defined Network (OpenShift SDN) for direct network routing to pods.
Configuring Ingress Controller
You must set up an ingress controller to manage all the HTTP and WebSocket ingress traffic. The ingress controller you choose must have the following properties:
- Cookies usage
- Header requirements - client IP and redirect, and passthrough
- Session stickiness
- Allowlisting (optional)
- TLS for ingress (optional) - ability to enable or disable TLS on the connection.
You can define these parameters in the values.yaml file for applicable services. For more information, see the related service-level guides.
DNS and Service Mesh
Genesys recommends having a CoreDNS within the Kubernetes clusters along with Node LocalDNS for performance.
Genesys Engage services require Consul Service Mesh that dynamically routes traffic to the right available service instance.
Genesys does not supply or enforce any network policy. You can create your own network policy for services that require a network policy and configure them in the Helm v3 charts.
For more information about network policy requirements, see the related service-level guides.