PrivateEdition/Current/PEGuide/ConfigNetwork - Revision history

WikiSysop at 04:01, March 31, 2023

2023-03-31T04:01:56Z

Uma.jayakumar.IX: Published

2021-12-22T19:14:10Z

Published

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

2021-11-09T21:11:54Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:29:28Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Tanya.ivanova@genesys.com: Published

2021-08-20T18:12:24Z

Published

Uma.jayakumar@genesys.com: Published

2021-08-02T14:16:37Z

Published

Uma.jayakumar@genesys.com: Published

2021-06-30T19:16:27Z

Published

Uma.jayakumar@genesys.com: Published

2021-06-30T18:51:03Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Network settings
|Context=TBD
|ComingSoon=No
|Section={{Section
|sectionHeading=Setting up Container Networking Interface
|alignment=Vertical
|structuredtext=When you create the OpenShift cluster(s) to deploy the Genesys Engage services, configure the cluster to support the Container Network Interface (CNI) or its equivalent. In a Kubernetes environment, CNI allows direct network routing to pods in a node via private IPs. Besides routing, CNI also removes the allocated resources to a container when it is deleted. When you use a CNI, you don't have to rely on kubenet and/or Calico for Pod routing.

Genesys Voice related connections from external systems/services, for example, Session Border Controller (SBC) requires CNI.

//Are we recommending any CNI provider?//

Any special requirements for the CNI deployment need to be documented, if applicable. //Platform team must provide this detail.//

<br />
|Status=No
}}{{Section
|sectionHeading=Subnet sizing
|alignment=Vertical
|Status=No
}}{{Section
|sectionHeading=Configuring Ingress Controller
|alignment=Vertical
|structuredtext=An ingress controller is required. This used for all HTTP and Websocket ingress traffic. The following are specific capabilities that the ingress controller implementation should have:

There will be a Helm override attributes to allow a customer to set this for each service.

Describe the following Ingress properties

*Cookies usage
*Header requirements - client IP & redirect, passthrough
*Session stickiness
*Whitelisting - optional
*TLS for ingress - optional (should be able to enable or disable TLS on the connection).

<br />
|Status=No
}}{{Section
|sectionHeading=Network Policy
|alignment=Vertical
|structuredtext=Genesys does not supply or enforce any Network Policy. Customers are encouraged to create their own network policy for specific services that require a network policy and configure them in the Helm v3 charts.

For more details, refer the respective service-level documentation of the service.

<br />
|Status=No
}}{{Section
|sectionHeading=Connections external to Kubernetes clusters
|alignment=Vertical
|structuredtext=Requirement:

Any external connection from the Kubernetes cluster to other systems need to be documented. This will include connecting to Genesys Cloud for Hybrid services (such as AI, WEM) as well as "Mixed" Environments where some components are still deployed as VMs. Need to specify the port(s) and protocols.

Note that this will include 3rd party services. Customers may optionally deploy these services outside of the Kubernetes cluster especially for production environments. These connections must be secured.

Note that Mixed Environments will mainly be for transition periods when customers are migrating from a classic premise environment to Private Edition.
|Status=No
}}{{Section
|sectionHeading=DNS and Service Mesh
|alignment=Vertical
|structuredtext====DNS===
CoreDNS is recommended with in the Kubernetes clusters along with Node LocalDNS for performance.

===Service Mesh===
Engage Services are dependent on a Service Mesh in particular Consul to dynamically route traffic to the right available service instance. In the future it might be used to enable TLS between services as well as richer network access control between services.
|Status=No
}}
}}

@@ Line 7: / Line 7: @@
 |sectionHeading=Enabling Container Networking Interface
 |alignment=Vertical
-|structuredtext=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.<br />
+|structuredtext=In your Kubernetes cluster, enable Container Networking Interface (CNI) or its equivalent to establish communication between pods in the cluster. <br />
 |Status=No
 }}{{Section

@@ Line 12: / Line 12: @@
 |sectionHeading=Configuring Ingress Controller
 |alignment=Vertical
-|structuredtext=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:
+|structuredtext=You must set up an ingress controller to manage all the HTTP and WebSocket ingress traffic, and to support Cluster IP. The ingress controller you choose must have the following properties:
 *Cookies usage
@@ Line 29: / Line 29: @@
 ===Service Mesh===
-Genesys Multicloud CX services require Consul Service Mesh that dynamically routes traffic to the right available service instance.
+Genesys Multicloud CX services require Consul Service Mesh that dynamically routes traffic to the right available service instance. Deploy Consul Service Mesh within the cluster where Genesys Multicloud CX services are deployed.
 |Status=No
 }}{{Section
@@ Line 36: / Line 36: @@
 |structuredtext=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.
+For more information about network policy requirements, see the related {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=GEServices|display text=service-level guides}}.
 |Status=No
-}}{{Section
+}}
 |sectionHeading=OpenShift settings
 |alignment=Vertical
@@ Line 44: / Line 47: @@
 |Status=No
 }}
 }}

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Network settings
-|Context=Describes the network settings required for Kubernetes clusters in Genesys Engage cloud private edition. For more information about networking outside Kubernetes clusters, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=NetworkOverview}}.
+|Context=Describes the network settings required for Kubernetes clusters in Genesys Multicloud CX private edition. For more information about networking outside Kubernetes clusters, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=NetworkOverview}}.
 |ComingSoon=No
 |Section={{Section