User: Jdruker/enableServiceLinksNote

From Genesys Documentation
Jump to: navigation, search

Suggested content for Creating namespaces[ | edit source]

Cleaned up[ | edit source]

To deploy the Genesys Multicloud CX private edition services, create a namespace per service group and deploy the associated services within that namespace. Alternatively, in OpenShift deployments you can create a single namespace for all private edition services and deploy them within that namespace.

Important
If you use a single namespace, ensure that all private edition services have the enableServiceLinks parameter in the pod specification set to false, in order to avoid environment variable conflicts. This is the default setting in the Helm charts for all services. In some services the parameter is configurable in the values.yaml file.

With change tracking[ | edit source]

For deploying To deploy the Genesys Multicloud CX private edition services, create a namespace per service group and deploy the associated services within that namespace. Alternatively, in OpenShift deployments you can also create a single namespace for all Genesys Multicloud CX private edition services and deploy them within that namespace.

Important
If you use a single namespace, ensure that all private edition services have the enableServiceLinks parameter in the pod specification set to false, in order to avoid environment variable conflicts. This is the default setting in the Helm charts for all services. In some services the parameter is configurable in the values.yaml file.