Difference between revisions of "GWS/Current/GWSPEGuide/ConfigureIngress"
m (Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX") |
|||
| Line 10: | Line 10: | ||
|structuredtext=You can specify parameters for the deployment by overriding Helm chart values in the '''values.yaml''' file. <!-- See the tables below for a full list of overridable values available for each container in GWS Ingress.--> | |structuredtext=You can specify parameters for the deployment by overriding Helm chart values in the '''values.yaml''' file. <!-- See the tables below for a full list of overridable values available for each container in GWS Ingress.--> | ||
| − | For more information about how to override Helm chart values, see {{SuiteLevelLink|helmoverride}} in the ''Setting up Genesys | + | For more information about how to override Helm chart values, see {{SuiteLevelLink|helmoverride}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide. |
If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the '''values.yaml''' file, so that no user or group IDs are specified. For details, see {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress|anchor=security|display text=Configure security}} below. | If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the '''values.yaml''' file, so that no user or group IDs are specified. For details, see {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress|anchor=security|display text=Configure security}} below. | ||
| Line 27: | Line 27: | ||
|anchor=security | |anchor=security | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |structuredtext=To learn more about how security is configured for private edition, be sure to read the {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=Prerequisites|display text=Permissions}} and {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}} topics in the ''Setting up Genesys | + | |structuredtext=To learn more about how security is configured for private edition, be sure to read the {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=Prerequisites|display text=Permissions}} and {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}} topics in the ''Setting up Genesys Multicloud CX Private Edition'' guide. |
The security context settings define the privilege and access control settings for pods and containers. | The security context settings define the privilege and access control settings for pods and containers. | ||
Revision as of 20:31, November 9, 2021
Contents
Learn how to configure GWS Ingress.
Override Helm chart values
You can specify parameters for the deployment by overriding Helm chart values in the values.yaml file.
For more information about how to override Helm chart values, see Overriding Helm chart values in the Setting up Genesys Multicloud CX Private Edition guide.
If you want to use arbitrary UIDs in your OpenShift deployment, you must override the securityContext settings in the values.yaml file, so that no user or group IDs are specified. For details, see Configure security below.
Configure Kubernetes
Create a Kubernetes secret for your API token from Consul. For more information about this token, see Consul's access control documentation.
kubectl create secret generic gws-secrets-green -n gws --from-literal='gws-consul-token=<token-from-consul>'Configure security
To learn more about how security is configured for private edition, be sure to read the Permissions and OpenShift security settings topics in the Setting up Genesys Multicloud CX Private Edition guide.
The security context settings define the privilege and access control settings for pods and containers.
By default, the user and group IDs are set in the values.yaml file as 500:500:500, meaning the genesys user.
deploymentGlobals:
securityContext:
runAsUser: 500
runAsGroup: 500
fsGroup: 500
runAsNonRoot: trueArbitrary UIDs in OpenShift
If you want to use arbitrary UIDs in your OpenShift deployment, you must override the securityContext settings in the values.yaml file, so that you do not define any specific IDs.
deploymentGlobals:
securityContext:
runAsUser: null
runAsGroup: 0
fsGroup: null
runAsNonRoot: true