Genesys Documentation - User contributions [en]

https://all.docs.genesys.com/api.php?action=feedcontributions&feedformat=atom&user=Jumunn Genesys Documentation - User contributions [en] 2026-05-23T20:30:17Z User contributions MediaWiki 1.31.1 https://all.docs.genesys.com/index.php?title=GWS/Current/GWSPEGuide/DeployIngress&diff=124267 GWS/Current/GWSPEGuide/DeployIngress 2022-07-08T16:26:53Z

<p>Jumunn: Published</p> <hr /> <div>{{ArticlePEServiceDeploy<br /> |ServiceId=11ff3d39-ae2b-4526-b7e5-7dcdf781ef01<br /> |IncludedServiceId=1dd952ea-ff42-44ac-9046-ca5786df98c8<br /> |IncludeAssumptions=Yes<br /> |Section={{Section<br /> |alignment=Vertical<br /> |structuredtext={{NoteFormat|If you are deploying Genesys Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.|3}}<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Prerequisites<br /> |anchor=prerequisites<br /> |alignment=Vertical<br /> |structuredtext=Before you deploy GWS ingress, you must first {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}} and {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}.<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Deploy<br /> |anchor=deploy<br /> |alignment=Vertical<br /> |structuredtext=To deploy GWS ingress, you need the GWS ingress Helm package and override file. Copy '''values.yaml''' and the Helm package ('''gws-ingress-<version>.tgz''') to the installation location.<br /> <br /> For OpenShift, select the '''gws''' project you created in {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy|anchor=OpenShift|display text=Prepare your environment}}:<br /> oc project gws<br /> Run the following command to deploy GWS ingress:<br /> helm upgrade --install gws-ingress <helm_directory>/gws-ingress --version=<version> -n gws -f ./override.gws-ingress.values.yaml -f ./versions.yaml<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Create routes in OpenShift<br /> |anchor=https<br /> |alignment=Vertical<br /> |structuredtext=Follow the instructions to configure external access to GWS ingress in OpenShift. <br /> <br /> Genesys recommends using the following hostname format: <code>gws.<cluster-subdomain></code>. For example, the VCE cluster (<nowiki>https://console-openshift-console.apps</nowiki>.<yourclusterdomain>.com/) should have the hostname '''gws.<yourclusterdomain>.com'''<br /> <br /> oc create route edge --service=gws-service-proxy --hostname=<hostname><br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Validate the deployment<br /> |alignment=Vertical<br /> |structuredtext=First, check that the pod is running:<br /> <br /> kubectl get pod<br /> <br /> The result should show that gws-service-proxy is running. For example:<br /> <br /> gws-service-proxy-d5997957f-m4kcg 1/1 Running 0 4d13h<br /> <br /> Check the service:<syntaxhighlight><br /> kubectl get svc<br /> </syntaxhighlight>The result should display the service name, gws-service-proxy. For example:<br /> <br /> gws-service-proxy ClusterIP 10.202.55.20 <none> 80/TCP,81/TCP,85/TCP,86/TCP 4d13h<br /> <br /> Check the '''gws-ingress''' status:<br /> helm status gws-ingress -n gws<br /> <br /> The result should show the namespace details with a status of deployed:<br /> <br /> <syntaxhighlight>NAME: gws-ingress<br /> LAST DEPLOYED: Fri Sep 17 11:54:31 2021<br /> NAMESPACE: gws<br /> STATUS: deployed<br /> REVISION: 1<br /> TEST SUITE: None</syntaxhighlight><br /> <br /> Check the installed Helm release:<br /> helm list –n gws<br /> <br /> The result should show the '''gws-services''' and '''gws-ingress''' deployment details. For example:<br /> <syntaxhighlight><br /> <br /> NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION<br /> <br /> gws-ingress gws 1 2021-09-17 11:54:31.339091 -0300 ADT deployed gws-ingress-0.2.7 1.0 <br /> <br /> gws-services gws 1 2021-09-17 11:43:50.0692273 -0300 ADT deployed gws-services-1.0.55 1.0<br /> </syntaxhighlight><br /> Check the GWS Kubernetes objects created by Helm:<br /> kubectl get all -n gws<br /> The result should show all the created pods, services, ConfigMaps, and so on.<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Next steps<br /> |anchor=next<br /> |alignment=Vertical<br /> |structuredtext=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}<br /> |Status=No<br /> }}<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=AUTH/Current/AuthPEGuide/Configure&diff=120976 AUTH/Current/AuthPEGuide/Configure 2022-05-27T19:43:04Z

<p>Jumunn: Published</p> <hr /> <div>{{Article<br /> |Standalone=No<br /> |DisplayName=Configure Genesys Authentication<br /> |Context=Learn how to configure Genesys Authentication.<br /> |ComingSoon=No<br /> |Section={{Section<br /> |alignment=Vertical<br /> |structuredtext=Complete the steps on this page to configure your Genesys Authentication deployment.<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Add Java KeyStore support (optional)<br /> |anchor=jks<br /> |alignment=Vertical<br /> |structuredtext=Complete the steps in this section to set up a [https://en.wikipedia.org/wiki/Java_KeyStore Java KeyStore] (JKS) if you need to configure Genesys Authentication to use [https://jwt.io/ JSON Web Token] authentication. This method of authentication is currently used for {{Link-AnywhereElse|product=WebRTC|version=Current|manual=WebRTCPEGuide|display text=WebRTC}}.<br /> <br /> Create a keystore file:<br /> <br /> <source lang="text">keytool -keystore idp_keystore.jks -genkey -alias gws-auth-key -storepass <password> -keypass <password> -keyalg RSA</source><br /> <br /> Get the Base64 encoded key:<br /> <br /> <source lang="text">cat ./idp_keystore.jks | base64</source><br /> <br /> The result looks like this:<br /> <br /> <source lang="text">/u3+7QAAAAIAAAABAAAAAQAMZ3dzLWF1dGgta2V5AAABeRmB2Y4AAAUBMIIE/TAOBgorBgEEASoCEQEBBQAEggTpwQQ5aW5CUYAsf4/IheBuNrlPPyZhUA+NWh3SG52HV3sVjV+p18vKp2k/q12I9NynoM6R/DW5bFfEWU1zx3cfXH2kNirRUOIbNZpa43NOroyyF1GSdZFlwa8Kq8Xtp8ZBmiJdSb1n12ODaTKGKv1cb5tsfdzkWs99QeTBGJypHMCdnBvdFB0Nvid+yaxdmK3bdQlCwDgDOHZ2RnU0oxXebH3o+jIrrowyo7DidJDyUwIeT2PPPI9F88QsP+CdDRRR1T7t0ojd1hIJ8YYMwJ1wQmwgF4QZRbtrEnwXqkHinJnwOERcp4FLuceds6YTlcxvWsS+GEv38Jv8YokLwRb/mMACTHk4R9yASsd7fljgNLSn0jhrz9FuxvYgpOVvExiq+sb5YrfbZjtTzZDzFVOu/2kWzASfZBSiyyxMOr3IhUPkMpIrg+UYkI0tgn/C3yR1wLr9HElpx8fCu61ORqp8hhp1yvL46K0c6eTa2JcRpO6fmysf2EG0JagG7zNEJHlvtNnt3JpQV06xos2iWsFAtHq+9w8LwvCVbDzx/UHoCYenIdJ7SBv06mXgKisa3RDIi/y5x5/9T4brgCLUvwI4Z5Rf/oi2Zx5/lXjQXmBPlPAcUVHLr5PvNQUUx5NBr/ooioD7qka4ADF1/cx8I2bzqTi+U01fiFdMGRlNlCfcGDMI2h82JUeCswRYi4+dMDiSaGgC2MoL2susLxMYa5CTo9Vs0Y2k+6j8fhIO4h8h0JxdXZODU63OM0cDSUHXfbyKSey/4IhiV3k7W4OHYeXUeDvoNmfo/AriELZl+WgYETiXGsKzxmrsHrBKC0+aT098FwqdY9ACsM/7WoF2+9eftc7fa2jruutrRjmk0A/BaIqzboJLFiWaUUGV9gsexEmpGszikQsmOYSIRxY8BYF+SYldehcfcsRRxDnhTaGNV8y2ZnwA61FNPAFps3gaFXeaYsUzlxTSi9m70HJJrUp7JDK6SGg6luiKMG4O7QjsGgOOwGpoLJf7EFOCspN3t4damhH/KFi9OrEuAdhMJa+iQ21PBZ+iIwxb0y9xMReImoUtoqy6Epre3qMOS6MILLw2bVrxJYo38+hR5uzNdlbsUlpYOoorI1Hp8A/VEYtG9PDHEhhoqUamdUYUzkFDi9QZfylIgi8Jc4G4PPrPKgMPqqE7sl6bJvoLavU58eHpdWo/Mb9UtdTx+l/SlulCCE0Xce6M9YE1SyC2B3gd82zNQa81lx+QAY8IaSmX+C2nMz+UeXKngSEzguK6gXg9RwCs8pUavuLQ6uZGkJ+fhDBvDAFgD7hG1XdHs27XGSUsRq6GiiwmjZXsZ70ETIVmXfuSvGuYYpv4CKzIDvweGdbkUWap2oQqm6Sw+OkJLbim1aW4MSYGCZItLOM36108onELop0wTIMiZBv2cIaQ+WzbyKDXIi94ebntxu42GSeUn1IGDMGAa+vh4itLDV6yIXCRHCd9GM6JBj+SKXkn+J0FIZ257Kf4k3kg6rm9Ha1800NMB7ILrbJChCZd5bmDmMwUGsNrlar2Oa4S41Y81vmBQJlMzSvAS37gk3eFX3XLKtfn7+Dxq8aYRA0TQEMln0uUuoiNRZH8iaLwhpI4bEkaoSU/DT/KHRB7AHN5/vQpj6KOscxqmyPrgPY/+TseczEeaQLQ6MfjvXY+AAAAAQAFWC41MDkAAAN7MIIDdzCCAl+gAwIBAgIEYxhLHTANBgkqhkiG9w0BAQsFADBsMRAwDgYDVQQGEwdVbmtub3duMRAwDgYDVQQIEwdVbmtub3duMRAwDgYDVQQHEwdVbmtub3duMRAwDgYDVQQKEwdVbmtub3duMRAwDgYDVQQLEwdVbmtub3duMRAwDgYDVQQDEwdVbmtub3duMB4XDTIxMDQyODE3MjMzMFoXDTIxMDcyNzE3MjMzMFowbDEQMA4GA1UEBhMHVW5rbm93bjEQMA4GA1UECBMHVW5rbm93bjEQMA4GA1UEBxMHVW5rbm93bjEQMA4GA1UEChMHVW5rbm93bjEQMA4GA1UECxMHVW5rbm93bjEQMA4GA1UEAxMHVW5rbm93bjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0300E4F3NDKRHYwrkqDgeUPwoIrozyLp6JvkCsOe1nj5L44vwJjnrYw9falOVDQ9ggwquwXoD5RNEf5/esYcJNEqu1btJLwLvhXb651OyZnsmeNGP2BrNCPXZS6CBReMMKJaZrlCwJQxiSrGPHB/gpxKoAowLwl3V7wB2BHKDhrczQBPdvtsfBAzeqpN/yRpdKZRAtu2LyGqRZKCglSrwYenJFqROdOeworbNmtIKXfQLiamE4KdhzQdPfnyBC7ZWtCIJUp9Va4LmCYD/ISOmVyfQ9Xql1rRNQLcVaewCKRM2ffBAkx98d3n79XUZDljOzHh+79tCpheuuYfbMQqMCAwEAAaMhMB8wHQYDVR0OBBYEFNtM8mIEb67VYot5tjDAdrhiq+31MA0GCSqGSIb3DQEBCwUAA4IBAQBued3SqK+1chAUpNz06Ceak2Ldzlz6MXxBZx6fx50odSY3C4rwywK31RSAAtCe/Ta4y+B6JcdPjFtII6Pf5W0DDTOa3cHNMeukYn5lBnaMbIKqoxFT7nM7MD3DB+dISvMu8FtVWFwbPzXWhl+Aycuu9ETGlCoJqYfl+vmLyGjJVadcUg4E3u7b29woO+bH9pagJErfi7Wq0vaaqMtkKjfOSovMTwz5ruXSiCDZlxb8C8CEr9lkpT3F0G1XFaNNOHoZiZNwXFKLoLrdI2t3pOCYyhwYbGKGMyitRguYz490dxZ0G5R4kMo/YbN7be2QIJwmucIZzH7fkU90V+rmVZhl9Bo8ixuIJG/vZTxmEBaDqmhiP4w=</source><br /> Make note of the following values - you need them to configure JKS support in the {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=Override|display text=Helm chart}}:<br /> <br /> *Keystore filename<br /> *Keystore password<br /> *Key alias<br /> *Key password<br /> *Base64 encoded key<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Configure a secret to access JFrog<br /> |anchor=Secret<br /> |alignment=Vertical<br /> |structuredtext=If you haven't done so already, create a secret for accessing the JFrog registry:<br /> <source lang="text">kubectl create secret docker-registry <credential-name> --docker-server=<docker repo> --docker-username=<username> --docker-password=<password> --docker-email=<emailid></source><br /> <br /> Now map the secret to the default service account:<br /> <source lang="text">kubectl secrets link default <credential-name> --for=pull</source><br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Override Helm chart values<br /> |anchor=Override<br /> |alignment=Vertical<br /> |structuredtext=You can specify parameters for the deployment by overriding Helm chart values in the '''values.yaml''' file. See the '''Parameters''' table for a full list of overridable values.<br /> <br /> For more information about how to override Helm chart values, see {{SuiteLevelLink|helmoverride}} in the {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide}} guide.<br /> <br /> 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=AuthPEGuide|topic=Configure|anchor=Security|display text=Configure security}} below.<br /> {{{!}} class="wikitable" style="table-layout: fixed; overflow-wrap: break-word;" {{!}}<br /> {{!}}+<br /> Parameters<br /> !Parameter<br /> !Description<br /> !Valid values<br /> !Default<br /> {{!}}-<br /> {{!}}gws-core-auth<br /> {{!}}The gws-core-auth image version tag. For example, 100.0.003.3508.<br /> {{!}}A valid image version<br /> {{!}}""<br /> {{!}}-<br /> {{!}}gws-core-environment<br /> {{!}}The gws-core-environment image version tag. For example, 100.0.003.1866.<br /> {{!}}A valid image version<br /> {{!}}""<br /> {{!}}-<br /> {{!}}gws-ui-auth<br /> {{!}}The gws-ui-auth image version tag. For example, 100.0.003.1328.<br /> {{!}}A valid image version<br /> {{!}}""<br /> {{!}}-<br /> {{!}}image.imagePullSecrets<br /> {{!}}The secret Kubernetes uses to get credentials to pull images from the registry.<br /> {{!}}A valid secret<br /> {{!}}[]<br /> {{!}}-<br /> {{!}}image.pullPolicy<br /> {{!}}Specifies when Kubernetes pulls images from the registry on start up.<br /> {{!}}IfNotPresent or Always<br /> {{!}}"IfNotPresent"<br /> {{!}}-<br /> {{!}}image.registry<br /> {{!}}Docker registry address<br /> {{!}}A valid registry URL<br /> {{!}}""<br /> {{!}}-<br /> {{!}}{{AnchorDiv|consul}}consul.discovery_register<br /> {{!}}Specifies whether services are registered in Consul.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}consul.discovery_tenants<br /> {{!}}Enables tenant discovery through Consul.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}consul.enabled<br /> {{!}}Enables a connection to Consul.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}consul.host<br /> {{!}}The host of the local Consul agent.<br /> {{!}}A valid URL<br /> {{!}}"<nowiki>http://$(K8_HOST_IP)</nowiki>"<br /> {{!}}-<br /> {{!}}consul.port<br /> {{!}}The port of the local Consul agent.<br /> {{!}}A valid port<br /> {{!}}8500<br /> {{!}}-<br /> {{!}}consul.require_token<br /> {{!}}Specifies whether Genesys Authentication reads the API token from a Kubernetes secret.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}consul.secret.create<br /> {{!}}Create or use an existing secret with the Consul API token.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}consul.secret.name_override<br /> {{!}}The name of the Kubernetes secret for Consul.<br /> {{!}}A valid secret name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}consul.secret.token<br /> {{!}}The API token to access Consul.<br /> {{!}}A valid API token<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}ingress.enabled<br /> {{!}}Enables external ingress for Genesys Authentication.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}{{AnchorDiv|ingress.frontend}}ingress.frontend<br /> {{!}}The host that is used by external ingress.<br /> {{!}}A valid host<br /> {{!}}"gauth.local"<br /> {{!}}-<br /> {{!}}ingress.annotations.<br /> {{!}}Annotations that are applied to external ingress. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}nginx.ingress.kubernetes.io/proxy-body-size: "0"<br /> {{!}}-<br /> {{!}}ingress.tls_enabled<br /> {{!}}Enables Transport Layer Security (TLS) on external ingress.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}ingress.tls<br /> {{!}}The name of the secret for Secure Sockets Layer (SSL) certificates.<br /> {{!}}A valid secret name<br /> {{!}}<syntaxhighlight><br /> - hosts:<br /> - gauth.local<br /> secretName: letsencrypt<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}internal_ingress.enabled<br /> {{!}}Enables internal ingress for Genesys Authentication.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}{{AnchorDiv|internal_ingress.frontend}}internal_ingress.frontend<br /> {{!}}The host that is used by internal ingress.<br /> {{!}}A valid host<br /> {{!}}"gauth-int.local"<br /> {{!}}-<br /> {{!}}internal_ingress.annotations<br /> {{!}}Annotations that are applied to internal ingress. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}nginx.ingress.kubernetes.io/proxy-body-size: "0"<br /> {{!}}-<br /> {{!}}{{AnchorDiv|internal_ingress.tls_enabled}}internal_ingress.tls_enabled<br /> {{!}}Enables Transport Layer Security (TLS) on internal ingress.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}internal_ingress.tls<br /> {{!}}The name of the secret for Secure Sockets Layer (SSL) certificates.<br /> {{!}}A valid secret name<br /> {{!}}<syntaxhighlight><br /> - hosts:<br /> - gauth-int.local<br /> secretName: letsencrypt<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}monitoring.enabled<br /> {{!}}Specifies whether to deploy Custom Resource Definitions (CRD) for ServiceMonitors to determine which services should be monitored.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}monitoring.interval<br /> {{!}}The interval at which Prometheus scrapes metrics.<br /> {{!}}A duration in seconds<br /> {{!}}"15s"<br /> {{!}}-<br /> {{!}}monitoring.alarms<br /> {{!}}Specifies whether to deploy CRD for PrometheusRules to define rules for alarms.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}monitoring.alarmThresholds.redisKeys<br /> {{!}}The threshold to trigger an alarm on the total number of keys in Redis.<br /> {{!}}Number<br /> {{!}}5000000<br /> {{!}}-<br /> {{!}}monitoring.alarmThresholds.redisMaxMemoryPerentage<br /> {{!}}The threshold to trigger an alarm for used Redis memory.<br /> {{!}}Number<br /> {{!}}85<br /> {{!}}-<br /> {{!}}monitoring.dashboards<br /> {{!}}Specifies whether to deploy ConfigMaps with Grafana Dashboards.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}monitoring.pagerduty<br /> {{!}}Enables alarms with a severity of <code>CRITICAL</code>.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}optional.affinity<br /> {{!}}Specifies the affinity and anti-affinity for Genesys Authentication pods. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> podAntiAffinity:<br /> preferredDuringSchedulingIgnoredDuringExecution:<br /> - podAffinityTerm:<br /> labelSelector:<br /> matchLabels:<br /> gauth: '{{ .gauth }}'<br /> app.kubernetes.io/name: '{{ include "auth.name" . }}'<br /> app.kubernetes.io/instance: '{{ .Release.Name }}'<br /> topologyKey: failure-domain.beta.kubernetes.io/zone<br /> weight: 100<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}optional.dnsConfig<br /> {{!}}Specifies custom DNS settings for Genesys Authentication pods. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pods-dns-policy|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> options:<br /> - name: ndots<br /> value: "3"<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}optional.dnsPolicy<br /> {{!}}Specifies the DNS policy for Genesys Authentication pods. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pods-dns-policy|displaytext=Kubernetes documentation}} for details.<br /> {{!}}"Default", "ClusterFirst", "ClusterFirstWithHostNet", or "None"<br /> {{!}}"ClusterFirst"<br /> {{!}}-<br /> {{!}}optional.nodeSelector<br /> {{!}}The labels Kubernetes uses to assign pods to nodes. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/configuration/assign-pod-node/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}optional.priorityClassName<br /> {{!}}The class name Kubernetes uses to determine the priority of a pod relative to other pods. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid priority class name<br /> {{!}}""<br /> {{!}}-<br /> {{!}}optional.securityContext<br /> {{!}}Specifies the privilege and access control settings Genesys Authentication pods. See {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=Security|display text=Configure security}} for details.<br /> {{!}}Object<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}optional.strategy<br /> {{!}}Specifies details for the rolling update strategy Genesys Authentication uses to upgrade it containers. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> type: RollingUpdate<br /> rollingUpdate:<br /> maxSurge: 10<br /> maxUnavailable: 0<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}optional.tolerations<br /> {{!}}The tolerations Kubernetes uses for advanced pod scheduling. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}[]<br /> {{!}}-<br /> {{!}}podDisruptionBudget.create<br /> {{!}}Specifies whether to create a PodDisruptionBudget. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/tasks/run-application/configure-pdb/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}podDisruptionBudget.spec<br /> {{!}}Specifies the details of your PodDisruptionBudget. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/tasks/run-application/configure-pdb/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid spec that defines a value for either minAvailable or maxUnavailable. Do not specify .spec.selector because it is calculated by Helm.<br /> {{!}}minAvailable: 2<br /> {{!}}-<br /> {{!}}pod_autoscaler.auth.enabled<br /> {{!}}Enables the Horizontal Pod Autoscaler for the Authentication Service. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}pod_autoscaler.auth.maxReplicas<br /> {{!}}Specifies the maximum number of Authentication Service replicas the Horizontal Pod Autoscaler controller will scale.<br /> {{!}}Number<br /> {{!}}10<br /> {{!}}-<br /> {{!}}pod_autoscaler.auth.metrics<br /> {{!}}Specifies resource metrics the Horizontal Pod Autoscaler controller uses to scale Authentication Service pods up or down. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> - type: Resource<br /> resource:<br /> name: cpu<br /> target:<br /> type: Utilization<br /> averageUtilization: 350%<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}pod_autoscaler.environment.enabled<br /> {{!}}Enables the Horizontal Pod Autoscaler for the Environment Service. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}pod_autoscaler.environment.maxReplicas<br /> {{!}}Specifies the maximum number of Environment Service replicas the Horizontal Pod Autoscaler controller will scale.<br /> {{!}}Number<br /> {{!}}10<br /> {{!}}-<br /> {{!}}pod_autoscaler.environment.metrics<br /> {{!}}Specifies resource metrics the Horizontal Pod Autoscaler controller uses to scale Environment Service pods up or down. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> - type: Resource<br /> resource:<br /> name: cpu<br /> target:<br /> type: Utilization<br /> averageUtilization: 350%<br /> </syntaxhighlight><br /><br /> {{!}}-<br /> {{!}}postgres.deploy<br /> {{!}}Specifies whether to deploy PostgreSQL. Set this option for lab environments only.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}postgres.image<br /> {{!}}Specifies the Docker image to use in the lab environment if <code>postgres.deploy=true</code>.<br /> {{!}}A Docker image<br /> {{!}}"postgres:11-alpine"<br /> {{!}}-<br /> {{!}}postgres.configmap.create<br /> {{!}}Specifies whether Genesys Authentication creates a ConfigMap with PostgreSQL connection parameters. If the value is false, you must create the ConfigMap manually.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}postgres.configmap.name_override<br /> {{!}}The name of the ConfigMap.<br /> {{!}}A value name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}postgres.db<br /> {{!}}The name of Genesys Authentication's PostgreSQL database.<br /> {{!}}A valid database name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}postgres.host<br /> {{!}}The host of the PostgreSQL instance.<br /> {{!}}A valid host<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}postgres.port<br /> {{!}}The port of the PostgreSQL instance.<br /> {{!}}A valid port<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}postgres.username<br /> {{!}}The username to access Genesys Authentication's PostgreSQL database.<br /> {{!}}A valid username<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}postgres.password<br /> {{!}}The password to access Genesys Authentication's PostgreSQL database.<br /> {{!}}A valid password<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}postgres.secret.create<br /> {{!}}Specifies whether to create a Kubernetes secret with user credentials for PostgreSQL. If this value is false, you must create the secret manually.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}postgres.secret.name_override<br /> {{!}}The name of the PostgreSQL secret.<br /> {{!}}A valid name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}redis.cluster_nodes<br /> {{!}}The Redis nodes in your cluster. For example, "redis-cluster1:7000,redis-cluster2:7002".<br /> {{!}}A comma-separated list of "host:port" pairs<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}redis.configmap.create<br /> {{!}}Specifies whether to create a ConfigMap with connection parameters for Redis. If this value is false, you must create the ConfigMap manually.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}redis.configmap.name_override<br /> {{!}}The name of the Redis ConfigMap.<br /> {{!}}A valid name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}redis.deploy<br /> {{!}}Specifies whether to deploy a Redis cluster. Set this option for lab environments only.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}redis.image<br /> {{!}}Specifies the Docker image to use in the lab environment if <code>redis.deploy=true</code>.<br /> {{!}}A Docker image<br /> {{!}}"redis:5-stretch"<br /> {{!}}-<br /> {{!}}redis.password<br /> {{!}}The Redis password.<br /> {{!}}A valid password<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}redis.password_required<br /> {{!}}Specifies whether Genesys Authentication should read the Redis password from a Kubernetes secret.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}redis.secret.create<br /> {{!}}Specifies whether to create a Kubernetes secret with Redis password. If this value is false, you must create the secret manually.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}redis.secret.name_override<br /> {{!}}The name of the Redis secret.<br /> {{!}}A valid name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}{{AnchorDiv|redis.use_tls}}redis.use_tls<br /> {{!}}Enable or disable a TLS connection to the Redis cluster.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}serviceAccount.create<br /> {{!}}Specifies whether to create a service account.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}serviceAccount.name<br /> {{!}}The name of the service account to use.<br /> {{!}}A service account name<br /> {{!}}""<br /> {{!}}-<br /> {{!}}serviceAccount.annotations<br /> {{!}}Annotations to add to the service account. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of labels as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.initContainers<br /> {{!}}Optional init containers to add to Genesys Authentication deployments.<br /> {{!}}Object<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.location<br /> {{!}}Location of the deployment. For example, "/USW1".<br /> {{!}}A valid location.<br /> {{!}}"/"<br /> {{!}}-<br /> {{!}}services.replicas<br /> {{!}}The number of Genesys Authentication pod replicas to deploy.<br /> {{!}}Number<br /> {{!}}3<br /> {{!}}-<br /> {{!}}services.db.init<br /> {{!}}Enable automatic updates for the database schema.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}services.db.poolCheckoutTimeout<br /> {{!}}The database pool timeout.<br /> {{!}}Number<br /> {{!}}3000<br /> {{!}}-<br /> {{!}}services.db.poolSize<br /> {{!}}The database pool size.<br /> {{!}}Number<br /> {{!}}3<br /> {{!}}-<br /> {{!}}services.db.ssl<br /> {{!}}Enable or disable an SSL connection to PostgreSQL. See the {{#Widget:ExtLink|link=https://www.postgresql.org/docs/9.0/libpq-ssl.html|displaytext=PostgreSQL documentation}} for details about SSL modes.<br /> {{!}}disable, prefer, require, verify-ca, or verify-full<br /> {{!}}"disable"<br /> {{!}}-<br /> {{!}}services.auth.loglevel<br /> {{!}}Specifies the log level for the Authentication Service.<br /> {{!}}INFO, DEBUG, WARN<br /> {{!}}DEBUG<br /> {{!}}-<br /> {{!}}services.auth.deploymentAnnotations<br /> {{!}}Annotations for Authentication Service deployment objects. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.auth.env.GWS_AUTH_SECURITY_HTTP_SCHEME_HEADER_NAME<br /> {{!}}The name of the header with protocol. This value can be used when HTTPS is terminated by the load balancer.<br /> {{!}}A valid header name<br /> {{!}}"X-Forwarded-Proto"<br /> {{!}}-<br /> {{!}}services.auth.env.GWS_AUTH_timeouts_requestTimeoutMs<br /> {{!}}The Authentication Service request timeout.<br /> {{!}}A value in milliseconds<br /> {{!}}30000<br /> {{!}}-<br /> {{!}}services.auth.env.JAVA_TOOL_OPTIONS<br /> {{!}}Specifies JVM arguments to set in the JAVA_TOOL_OPTIONS environment variable.<br /> {{!}}Valid JVM arguments<br /> {{!}}"-XX:+PrintFlagsFinal -XX:+UseG1GC -Dfile.encoding=UTF-8 -XX:+ExitOnOutOfMemoryError -XX:MaxRAMPercentage=80.0"<br /> {{!}}-<br /> {{!}}services.auth.env.GWS_AUTH_logging_level_com_genesys_gws_v3<br /> {{!}}Specifies the log level for the Authentication Service.<br /> {{!}}INFO, DEBUG, WARN<br /> {{!}}DEBUG<br /> {{!}}-<br /> {{!}}services.auth.env.GWS_AUTH_http_headers_frame_options<br /> {{!}}Specifies the value of the X-Frame-Options HTTP response header.<br /> {{!}}SAMEORIGIN, DENY, DISABLE, ALLOW<br /> {{!}}ALLOW<br /> {{!}}-<br /> {{!}}services.auth.jks.enabled<br /> {{!}}Specifies whether Genesys Authentication uses Java KeyStore. See {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=jks|display text=Add JKS support}} for details. This value must be set to true for Security Assertion Markup Language single sign-on (SAML SSO) functionality.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}services.auth.jks.keyAlias<br /> {{!}}The name of the key alias in the keystore used by the Authentication Service. This value comes from {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=jks|display text=Add JKS support}}.<br /> {{!}}A valid key alias<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth.jks.keyPassword<br /> {{!}}The keystore password from {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=jks|display text=Add JKS support}}.<br /> {{!}}A valid keystore password<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth.jks.keyStore<br /> {{!}}The name of the Java keystore file from {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=jks|display text=Add JKS support}}.<br /> {{!}}A valid keystore name<br /> {{!}}"jksStorage.jks"<br /> {{!}}-<br /> {{!}}services.auth.jks.keyStorePassword<br /> {{!}}The keystore password from {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=jks|display text=Add JKS support}}.<br /> {{!}}A valid keystore password<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth.jks.secret.create<br /> {{!}}Specifies whether to create a new secret with the keystore file content and keystore credentials.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}services.auth.jks.keyStoreFileData<br /> {{!}}The Base64 encoded key value from {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=jks|display text=Add JKS support}}.<br /> {{!}}A valid key<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth.jks.secret.name<br /> {{!}}A Kubernetes secret name with the keystore credentials and content.<br /> {{!}}A valid secret name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth.jks.sso.enabled<br /> {{!}}Specifies whether to enable SAML SSO functionality.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}services.auth.livenessProbe<br /> {{!}}Specifies parameters for the livenessProbe. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> livenessProbe:<br /> httpGet:<br /> path: /health<br /> port: management<br /> initialDelaySeconds: 120<br /> periodSeconds: 10<br /> successThreshold: 1<br /> timeoutSeconds: 3<br /> failureThreshold: 3<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.auth.readinessProbe<br /> {{!}}Specifies parameters for the readinessProbe. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> readinessProbe:<br /> httpGet:<br /> path: /health<br /> port: management<br /> initialDelaySeconds: 30<br /> timeoutSeconds: 3<br /> periodSeconds: 10<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.auth.replicas<br /> {{!}}The number of Authentication Service pod replicas to deploy. This value overrides services.replicas.<br /> {{!}}Number<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth.resources<br /> {{!}}The requests and limits for Authentication Service pod resources. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> requests:<br /> cpu: 500m<br /> memory: 4Gi<br /> limits:<br /> cpu: "4"<br /> memory: 6Gi<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.auth.serviceAnnotations<br /> {{!}}Annotations for Authentication Service service objects. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.auth_ui.deploymentAnnotations<br /> {{!}}Annotations for Authentication UI deployment objects. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.auth_ui.env.GWS_NGINX_ENABLE_MAPPING<br /> {{!}}Use Consul to discover Auth Service<br /> {{!}}<br /> {{!}}"false"<br /> {{!}}-<br /> {{!}}services.auth_ui.livenessProbe<br /> {{!}}Specifies parameters for the livenessProbe. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.auth_ui.readinessProbe<br /> {{!}}Specifies parameters for the readinessProbe. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.auth_ui.replicas<br /> {{!}}The number of Authentication UI pod replicas to deploy. This value overrides services.replicas.<br /> {{!}}Number<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.auth_ui.resources<br /> {{!}}The requests and limits for Authentication UI pod resources. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> requests:<br /> cpu: 100m<br /> memory: 500Mi<br /> limits:<br /> cpu: 500m<br /> memory: 1Gi<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.auth_ui.serviceAnnotations<br /> {{!}}Annotations for Authentication UI service objects. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.environment.loglevel<br /> {{!}}Specifies the log level for the Environment Service.<br /> {{!}}INFO, DEBUG, WARN<br /> {{!}}INFO<br /> {{!}}-<br /> {{!}}services.environment.deploymentAnnotations<br /> {{!}}Annotations for Environment Service deployment objects. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}services.environment.env.JAVA_TOOL_OPTIONS<br /> {{!}}Specifies JVM arguments to set in the JAVA_TOOL_OPTIONS environment variable.<br /> {{!}}Valid JVM arguments<br /> {{!}}"-XX:+PrintFlagsFinal -XX:+UseG1GC -Dfile.encoding=UTF-8 -XX:+ExitOnOutOfMemoryError -XX:MaxRAMPercentage=80.0"<br /> {{!}}-<br /> {{!}}services.environment.env.GWS_ENVIRONMENT_logging_level_com_genesys_gws_v3<br /> {{!}}Specifies the log level for the Environment Service.<br /> {{!}}INFO, DEBUG, WARN<br /> {{!}}INFO<br /> {{!}}-<br /> {{!}}services.environment.force_writable<br /> {{!}}Ignore the Data Center topology in a single-region deployment.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}services.environment.livenessProbe<br /> {{!}}Specifies parameters for the livenessProbe. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> livenessProbe:<br /> httpGet:<br /> path: /health<br /> port: management<br /> initialDelaySeconds: 120<br /> periodSeconds: 10<br /> successThreshold: 1<br /> timeoutSeconds: 3<br /> failureThreshold: 3<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.environment.readinessProbe<br /> {{!}}Specifies parameters for the readinessProbe. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> readinessProbe:<br /> httpGet:<br /> path: /health<br /> port: management<br /> initialDelaySeconds: 30<br /> timeoutSeconds: 3<br /> periodSeconds: 10<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.environment.replicas<br /> {{!}}The number of Environment Service pod replicas. This value overrides services.replicas.<br /> {{!}}Number<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.environment.resources<br /> {{!}}The requests and limits for Environment Service pod resources. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}Object<br /> {{!}}<syntaxhighlight><br /> requests:<br /> cpu: 500m<br /> memory: 4Gi<br /> limits:<br /> cpu: "4"<br /> memory: 6Gi<br /> </syntaxhighlight><br /> {{!}}-<br /> {{!}}services.environment.serviceAnnotations<br /> {{!}}Annotations for Authentication Service service objects. See the {{#Widget:ExtLink|link=https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|displaytext=Kubernetes documentation}} for details.<br /> {{!}}A valid set of annotations as "name: value"<br /> {{!}}{}<br /> {{!}}-<br /> {{!}}{{AnchorDiv|services.secret.admin_password}}services.secret.admin_password<br /> {{!}}Encrypted password of the operational user. The password should be encrypted with bcrypt hashing with any number of rounds. You can generate an encrypted password on the following site: https://www.javainuse.com/onlineBcrypt<br /> {{!}}A valid password<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}{{AnchorDiv|services.secret.admin_username}}services.secret.admin_username<br /> {{!}}The username of an operational user.<br /> {{!}}Any valid username. For example, opsAdmin, clientAdmin, ops.<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.secret.client_id<br /> {{!}}The ID of an encrypted client secret.<br /> {{!}}Any valid client ID. For example, external_api_client, nexus_client, authclient.<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.secret.client_secret<br /> {{!}}The encrypted client secret. The client secret should be encrypted with bcrypt hashing with any number of rounds. You can generate an encrypted client secret on the following site:https://www.javainuse.com/onlineBcrypt<br /> {{!}}A valid client secret<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.secret.create<br /> {{!}}Specifies whether to create the Kubernetes secret with the credentials of the operational user and client ID.<br /> {{!}}true or false<br /> {{!}}true<br /> {{!}}-<br /> {{!}}services.secret.name_override<br /> {{!}}The name of the secret.<br /> {{!}}A valid name<br /> {{!}}nil<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.admin_user<br /> {{!}}The name of the secretProviderClass with the operational user credentials.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-gauth-admin-user"<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.client_credentials<br /> {{!}}The name of the secretProviderClass with the client credentials.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-gauth-client-credentials"<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.consul_token<br /> {{!}}The name of the secretProviderClass with the Consul token.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-consul-consul-gauth-token"<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.jks_credentials<br /> {{!}}The name of the secretProviderClass with the JKS credentials.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-gauth-jks-credentials"<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.jks_keyvault<br /> {{!}}The name of the secretProviderClass with the JKS keystore.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-gauth-jks-keyvault"<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.pg_user<br /> {{!}}The name of the secretProviderClass with PostgreSQL credentials.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-gauth-pg-user"<br /> {{!}}-<br /> {{!}}services.secrets.secretProviderClassNames.redis_password<br /> {{!}}The name of the secretProviderClass with the Redis password.<br /> {{!}}A valid class name<br /> {{!}}"keyvault-gauth-redis-password"<br /> {{!}}-<br /> {{!}}services.secrets.useSecretProviderClass<br /> {{!}}Specifies whether to read secrets from the secretProviderClass instead of Kubernetes secrets.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}}<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Configure Kubernetes<br /> |anchor=Kubernetes<br /> |alignment=Vertical<br /> |structuredtext=The sections below provide more information about configuring Kubernetes.<br /> <br /> ===ConfigMaps===<br /> Genesys Authentication includes separate ConfigMaps for PostgreSQL and Redis configuration.<br /> <br /> '''PostgreSQL - configmap-pg.yaml'''<br /> <source lang="text">{{- if or .Values.postgres.configmap.create .Values.postgres.deploy }}<br /> apiVersion: v1<br /> kind: ConfigMap<br /> metadata:<br /> name: {{ include "configmap.postgres" . }}<br /> namespace: {{ .Release.Namespace | quote }}<br /> labels:<br /> {{- include "gauth.labels" . | nindent 4 }}<br /> gauth: postgres<br /> data:<br /> db: {{ required "Missing required parameter 'postgres.password'" .Values.postgres.db |quote}}<br /> host: {{ default ( include "name.postgres" . ) .Values.postgres.host |quote}}<br /> port: {{ default ( include "port.postgres.service" . ) .Values.postgres.port |quote }}<br /> {{- end }}</source><br /> <br /> '''Redis - configmap-redis.yaml'''<br /> <source lang="text"><br /> {{ if or .Values.redis.configmap.create .Values.redis.deploy }}<br /> apiVersion: v1<br /> kind: ConfigMap<br /> metadata:<br /> name: {{ include "configmap.redis" . }}<br /> namespace: {{ .Release.Namespace | quote }}<br /> labels:<br /> {{- include "gauth.labels" . | nindent 4 }}<br /> gauth: redis<br /> data:<br /> cluster_nodes: {{ default ( include "service.redis" . ) .Values.redis.cluster_nodes | quote}}<br /> {{end}}</source><br /> <br /> ===Secrets===<br /> The following Genesys Authentication services artifacts are stored as Kubernetes secrets:<br /> <br /> *Administrator user credentials for the Authentication API and Environment API services.<br /> *OAuth 20 client IDs and client secrets for the Authentication API and Environment API services.<br /> *PostgreSQL database credentials for the Environment API service.<br /> *PostgreSQL database credentials for the Authentication API service.<br /> *Java keystore password for Authentication API service.<br /> *Credentials for access to a password-protected Redis (Access Key) for the Authentication API service.<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Configure security<br /> |anchor=Security<br /> |alignment=Vertical<br /> |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.<br /> <br /> The security context settings define the privilege and access control settings for pods and containers.<br /> <br /> By default, the user and group IDs are set in the '''values.yaml''' file as <tt>500:500:500</tt>, meaning the '''genesys''' user.<br /> <syntaxhighlight><br /> optional:<br /> securityContext:<br /> runAsUser: 500<br /> runAsGroup: 500<br /> fsGroup: 500<br /> runAsNonRoot: true<br /> </syntaxhighlight><br /> <br /> ===Arbitrary UIDs in OpenShift===<br /> 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.<br /> <syntaxhighlight><br /> optional:<br /> securityContext:<br /> runAsUser: null<br /> runAsGroup: 0<br /> fsGroup: null<br /> runAsNonRoot: true<br /> </syntaxhighlight><br /> For details about these parameters and possible values, see '''optional.securityContext.*''' in the {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Configure|anchor=Override|display text=Parameters}} table above.<br /> |Status=No<br /> }}<br /> |PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=AUTH/Current/AuthPEGuide/Metrics&diff=120673 AUTH/Current/AuthPEGuide/Metrics 2022-05-24T16:15:20Z

<p>Jumunn: Redirected page to AUTH/Current/AuthPEGuide/Observability</p> <hr /> <div>#REDIRECT [[AUTH/Current/AuthPEGuide/Observability]]<br /> {{Article<br /> |Standalone=No<br /> |DisplayName=Metrics<br /> |Context=Learn which metrics you should monitor for Genesys Authentication and when to sound the alarm.<br /> |ComingSoon=No<br /> |Section={{Section<br /> |alignment=Vertical<br /> |structuredtext={{Notices|Notice=PEComingSoon}}<br /> |Status=No<br /> }}<br /> |PEPageType=21ecf3f4-ef12-4276-8872-1e0e3af9561e<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=Draft:RN/DigitalChannels/100.0.118.0000&diff=120018 Draft:RN/DigitalChannels/100.0.118.0000 2022-05-06T16:41:03Z

<p>Jumunn: Jumunn moved page Draft:RN/DigitalChannels/100.0.118.0000 to Draft:RN/DigitalChannels/100.0.118.0865</p> <hr /> <div>#REDIRECT [[Draft:RN/DigitalChannels/100.0.118.0865]]</div>

Jumunn https://all.docs.genesys.com/index.php?title=GWS/Current/GWSPEGuide/ConfigureTLS&diff=119922 GWS/Current/GWSPEGuide/ConfigureTLS 2022-05-04T18:36:07Z

<p>Jumunn: Published</p> <hr /> <div>{{Article<br /> |Standalone=No<br /> |DisplayName=Configure connections with TLS and authentication<br /> |Context=Learn how to configure Transport Layer Security and Authentication for connections to third-party services and non-containerized Genesys servers.<br /> |ComingSoon=No<br /> |Section={{Section<br /> |alignment=Vertical<br /> |structuredtext=Genesys Web Services and Applications (GWS) supports secure connections to third-party services and legacy Genesys servers using Transport Layer Security (TLS) version 1.2. <br /> <br /> To enable TLS, you must download and unpack the '''gws-services''' Helm chart locally. Next, create any required certificates for the services and put the truststores under the '''gws-services''' directory of the unpacked chart. For example: '''gws-services/crts/gwsPlatformSettingPostgresTrustore.p12.''' Following this example, the setting for the PostgreSQL truststore would be: <code>secretsTls.postgres.truststores.gws-plaftom-setting-postgres-truststore: crts/gwsPlatformSettingPostgresTrustore.p12</code>{{NoteFormat|When you {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}, make sure to point to your local files during the installation.|}}Next, configure TLS by overriding Helm chart values in the '''values.yaml''' file. See {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureTLS|anchor=thirdpartyservices|display text=TLS for third-party services}} and {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureTLS|anchor=genesysservers|display text=TLS for legacy Genesys servers}} for details.<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=TLS for third-party services<br /> |anchor=thirdpartyservices<br /> |alignment=Vertical<br /> |structuredtext=GWS supports TLS connections to the third-party services Redis, PostgreSQL, and Elasticsearch. To enable TLS for these services, set the following parameters in the '''values.yaml''' file: <br /> <br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure|anchor=gwsServices.gwsAppProvisioning.postgres.enableTls|display text=gwsServices.gwsAppProvisioning.postgres.enableTls}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure|anchor=postgres.enableTls |display text=postgres.enableTls }}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure|anchor=elasticSearch.enableTls|display text=elasticSearch.enableTls}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure|anchor= redis.enableTls |display text= redis.enableTls }}<br /> <br /> You must also define the truststore paths and passwords in the tables below:{{AnchorDiv|redis}}<br /> ===Redis===<br /> {{{!}} class="wikitable" style="table-layout: fixed; overflow-wrap: break-word;" {{!}}<br /> !Parameter<br /> !Description<br /> !Valid values<br /> !Default<br /> {{!}}-<br /> {{!}}secretsTls.redis.enabled<br /> {{!}}Specifies whether a Kubernetes secret is created for the TLS connection to the Redis cluster.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}secretsTls.redis.truststores.gws-platform-datacollector-redis-truststore<br /> {{!}}The Redis client truststore path for the GWS Data Collector Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.truststores.gws-platform-ixn-redis-truststore<br /> {{!}}The Redis client truststore path for the GWS Interaction Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.truststores.gws-app-workspace-redis-truststore<br /> {{!}}The Redis client truststore path for the GWS Workspace Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.truststores.gws-app-provisioning-redis-truststore<br /> {{!}}The Redis client truststore path for Agent Setup.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.truststores.gws-platform-voice-redis-truststore<br /> {{!}}The Redis client truststore path for the GWS Voice Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.passwords.gws-platform-datacollector-redis-truststore-password<br /> {{!}}The Redis client truststore password for the GWS Data Collector Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.passwords.gws-platform-ixn-redis-truststore-password<br /> {{!}}The Redis client truststore password for the GWS Interaction Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.passwords.gws-app-workspace-redis-truststore-password<br /> {{!}}The Redis client truststore password for the GWS Workspace Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.passwords.gws-app-provisioning-redis-truststore-password<br /> {{!}}The Redis client truststore password for Agent Setup.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.redis.passwords.gws-platform-voice-redis-truststore-password<br /> {{!}}The Redis client truststore password for the GWS Voice Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}}<br /> {{AnchorDiv|postgres}}<br /> ===PostgreSQL===<br /> {{{!}} class="wikitable" style="table-layout: fixed; overflow-wrap: break-word;" {{!}}<br /> !Parameter<br /> !Description<br /> !Valid values<br /> !Default<br /> {{!}}-<br /> {{!}}secretsTls.postgres.enabled<br /> {{!}}Specifies whether a Kubernetes secret is created for the TLS connection to PostgreSQL.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}secretsTls.postgres.truststores.gws-platform-setting-postgres-truststore<br /> {{!}}The PostgreSQL client truststore path for the GWS Setting Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.postgres.passwords.gws-platform-setting-postgres-truststore-password<br /> {{!}}The PostgreSQL client truststore password for the GWS Setting Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.postgresprovisioning.enabled<br /> {{!}}Specifies whether a Kubernetes secret is created for the gws-app-provisioning TLS connection to PostgreSQL.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}secretsTls.postgresprovisioning.truststores.gws-app-provisioning-postgres-truststore<br /> {{!}}The PostgreSQL client truststore path for gws-app-provisioning.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.postgresprovisioning.passwords.gws-app-provisioning-postgres-truststore-password<br /> {{!}}The PostgreSQL client truststore password for gws-app-provisioning.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}}<br /> {{AnchorDiv|elasticsearch}}<br /> ===Elasticsearch===<br /> {{{!}} class="wikitable" style="table-layout: fixed; overflow-wrap: break-word;" {{!}}<br /> !Parameter<br /> !Description<br /> !Valid values<br /> !Default<br /> {{!}}-<br /> {{!}}secretsTls.elasticsearch.enabled<br /> {{!}}Specifies whether a Kubernetes secret is created for the TLS connection to the Elasticsearch cluster.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}secretsTls.elasticsearch.truststores.gws-platform-datacollector-elasticsearch-truststore<br /> {{!}}The Elasticsearch client truststore path for the GWS Data Collector Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}secretsTls.elasticsearch.passwords.gws-platform-datacollector-elasticsearch-truststore-password<br /> {{!}}The Elasticsearch client truststore password for the GWS Data Collector Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}}<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=TLS for legacy Genesys servers<br /> |anchor=genesysservers<br /> |alignment=Vertical<br /> |structuredtext=GWS supports TLS connections to legacy Genesys servers in a mixed mode environment. GWS uses the [https://docs.genesys.com/Documentation/PSDK Platform SDK] to connect to legacy Genesys servers, such as [https://docs.genesys.com/Documentation/FR Configuration Server], [https://docs.genesys.com/Documentation/IXN Interaction Server], [https://docs.genesys.com/Documentation/TS T-Server], [https://docs.genesys.com/Documentation/UCS Universal Contact Server], [https://docs.genesys.com/Documentation/RTME Stat Server], [https://docs.genesys.com/Documentation/ES Chat Server], and [https://docs.genesys.com/Documentation/OU Outbound Contact Server].<br /> <br /> GWS services use [https://docs.genesys.com/Documentation/PSDK/9.0.x/Developer/TLSQuickStart upgrade mode ports] for TLS connections between Platform SDK and legacy Genesys services, which means you cannot enable TLS in the GWS '''values.yaml''' file. Instead, [https://docs.genesys.com/Documentation/PSDK/9.0.x/Developer/TLSTLSParametersinConfigManager configure the TLS parameters] in Configuration Server.<br /> <br /> You must also define the truststore paths and passwords in the tables below:<br /> {{AnchorDiv|truststore}}<br /> ===Truststore paths===<br /> {{{!}} class="wikitable" style="table-layout: fixed; overflow-wrap: break-word;" {{!}}<br /> !Parameter<br /> !Description<br /> !Valid values<br /> !Default<br /> {{!}}-<br /> {{!}}psdk.enabled<br /> {{!}}Specifies whether a Kubernetes secret is created for TLS connections to legacy Genesys servers.<br /> {{!}}true or false<br /> {{!}}false<br /> {{!}}-<br /> {{!}}psdk.truststores.gws-platform-configuration-psdk-truststore<br /> {{!}}The PSDK client truststore path for the GWS Configuration Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.truststores.gws-platform-ixn-psdk-truststore<br /> {{!}}The PSDK client truststore path for the GWS Interaction Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.truststores.gws-platform-chat-psdk-truststore<br /> {{!}}The PSDK client truststore path for the Chat Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.truststores.gws-platform-ucs-psdk-truststore<br /> {{!}}The PSDK client truststore path for the UCS Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.truststores.gws-platform-voice-psdk-truststore<br /> {{!}}The PSDK client truststore path for the GWS Voice Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.truststores.gws-platform-statistics-psdk-truststore<br /> {{!}}The PSDK client truststore path for the GWS Statistics Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.truststores.truststores.gws-platform-datacollector-psdk-truststore<br /> {{!}}The PSDK client truststore path for the GWS Data Collector Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.gws-platform-ocs-psdk-truststore<br /> {{!}}The PSDK client truststore path for the GWS OCS Service.<br /> {{!}}A valid path to the truststore file, relative to the '''gws-services''' directory.<br /> {{!}}""<br /> {{!}}}<br /> {{AnchorDiv|passwords}}<br /> ===Truststore passwords===<br /> {{{!}} class="wikitable" style="table-layout: fixed; overflow-wrap: break-word;" {{!}}<br /> !Parameter<br /> !Description<br /> !Valid values<br /> !Default<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-configuration-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the GWS Configuration Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-ixn-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the GWS Interaction Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-chat-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the Chat Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-ucs-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the UCS Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-voice-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the GWS Voice Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-statistics-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the GWS Statistics Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-datacollector-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the GWS Data Collector Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}-<br /> {{!}}psdk.passwords.gws-platform-ocs-psdk-truststore-password<br /> {{!}}The PSDK client truststore password for the GWS OCS Service.<br /> {{!}}A valid password<br /> {{!}}""<br /> {{!}}}<br /> |Status=No<br /> }}<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=GWS/Current/GWSPEGuide/Planning&diff=119919 GWS/Current/GWSPEGuide/Planning 2022-05-04T18:34:36Z

<p>Jumunn: </p> <hr /> <div>{{PEPrerequisites<br /> |DisplayName=Before you begin<br /> |Context=Find out what to do before deploying Web Services and Applications.<br /> |LimitationsStatus=Yes<br /> |HelmStatus=No<br /> |HelmText=Web Services and Applications (GWS) in Genesys Multicloud CX private edition is made up of multiple containers and Helm charts. The pages in this "Configure and deploy" chapter walk you through how to deploy the following Helm charts:<br /> <br /> *GWS services (gws-services) - all the GWS components.<br /> *GWS ingress (gws-ingress) - provides internal and external access to GWS services. Internal ingress is used for cross-component communication inside the GWS deployment. It also can be used by other clients located inside the same Kubernetes cluster. External ingress provides access to GWS services to clients located outside the Kubernetes cluster. If you are deploying Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.<br /> <br /> GWS also includes a Helm chart for Nginx (wwe-nginx) for Workspace Web Edition - see the {{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide}} for details about how to deploy this chart. <br /> <br /> See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GWSHelm}} for the Helm chart versions you must download for your release.<br /> <br /> For information about downloading Helm charts from JFrog Edge, see {{SuiteLevelLink|helmchart}}.<br /> |ThirdPartyStatus=No<br /> |ThirdPartyText=Install the prerequisite dependencies listed in the '''Third-party services''' table before you deploy Web Services and Applications. See {{SuiteLevelLink|softwarereq}} for a full list of prerequisites and third-party services required by all Genesys Multicloud CX private edition services.<br /> |SectionThirdPartyItem={{SectionThirdPartyItem<br /> |ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce<br /> |Notes=You must configure additional options for Elasticsearch to support the Data Collector Service.<syntaxhighlight><br /> action.auto_create_index: false<br /> thread_pool.write.queue_size: -1<br /> </syntaxhighlight><br /> You can set up Elasticsearch as a shared or dedicated service. <br /> <br /> <br /><br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=3aee73ed-68e0-4c70-8693-2421c68b86cd<br /> |Notes=The Redis server must run in cluster mode. You can set up Redis as a shared or dedicated service.<br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283<br /> |Notes=You can set up PostgreSQL as a shared or dedicated service. <br /> <br /> <br /><br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca<br /> |Notes='''GWS supports Consul 1.8'''. Consul can be installed either inside or outside the Kubernetes cluster. GWS pods require a Consul agent that is running at the Kubernetes node and GWS only communicates with this Consul agent. You must configure a connection to the Consul server in the local Consul agent.<br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=bc90a902-fc45-4546-b05b-bba8f567dba2<br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=0ce020f7-57d0-430e-bd82-27bef7d7834c<br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=17ed8d61-7149-43bb-8f0e-199f7d206ec8<br /> }}{{SectionThirdPartyItem<br /> |ThirdPartyItem=f1d380bf-42b1-4b67-9d27-d574bad90c86<br /> }}<br /> |StorageStatus=No<br /> |StorageText=GWS uses PostgreSQL to store tenant information, Redis to cache session data, and Elasticsearch to store monitored statistics for fast access. If you set up any of these services as dedicated services for GWS, they have the following minimal requirements:<br /> <br /> ===PostgreSQL===<br /> <br /> *CPU: 2<br /> *RAM: 8 GB<br /> *HDD: 50 GB<br /> <br /> ===Redis===<br /> <br /> *2 nodes:<br /> **CPU: 2<br /> **RAM: 8 GB<br /> **HDD: 20 GB<br /> <br /> ===Elasticsearch===<br /> <br /> *3 "master" nodes:<br /> **CPU: 2<br /> **RAM: 8 GB<br /> **HDD: 20 GB<br /> *4 "data" nodes)<br /> **CPU: 4<br /> **RAM: 16 GB<br /> **HDD: 20 GB<br /> |NetworkStatus=No<br /> |NetworkText=GWS ingress objects support Transport Layer Security (TLS) version 1.2 for a secure connection between Kubernetes cluster ingress and GWS ingress. TLS is disabled by default, but you can configure it for internal and external ingress by overriding the '''entryPoints.internal.ingress.tls''' and '''entryPoints.external.ingress.tls''' sections of the {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress|anchor=override|display text=GWS ingress Helm chart}}.<br /> <br /> For example:<br /> entryPoints:<br /> external:<br /> ingress:<br /> tls:<br /> - secretName: gws-secret-ext<br /> hosts:<br /> - gws.genesys.com<br /> In the example above:<br /> <br /> *'''secretName''' is the name of the Kubernetes secret that contains the certificate. The secret is a prerequisite and must be created before you deploy GWS Ingress.<br /> *'''hosts''' is a list of the fully qualified domain names that should use the certificate. The list must be the same as the value configured for the '''entryPoints.external.ingress.hosts''' parameter.<br /> <br /> ===Cookies===<br /> GWS components use cookies for following purposes:<br /> <br /> *identify HTTP/HTTPS user sessions<br /> *identify CometD user sessions<br /> *support session stickiness<br /> |BrowserStatus=Yes<br /> |BrowserText={{Editgrn open}}JM: Are these browsers are supported for Agent Setup? Browser support for WWE is documented in the WWE guid for private edition: {{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide|topic=Planning}}. Also, can we align with the versions that are supposed to be supported for cloud/private edition in all products? Those versions are:{{Editgrn close}}<br /> <br /> *{{Editgrn open}}Chrome: Current release or one version previous<br /> *{{Editgrn open}}Firefox: Current release or one version previous<br /> *{{Editgrn open}}Microsoft Edge: Current release<br /> *{{Editgrn open}}Microsoft Edge Chromium: Current release <br /> <br /> <br /> You can use any of the following browsers for UIs:<br /> <br /> *Chrome 75+<br /> *Firefox 68+<br /> *Firefox ESR 60.9<br /> *Microsoft Edge<br /> |DependenciesStatus=No<br /> |DependenciesText=Genesys Web Services and Applications must be deployed after Genesys Authentication. <br /> <br /> For a look at the high-level deployment order, see {{SuiteLevelLink|deployorder}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide.<br /> |GDPRStatus=Yes<br /> |GDPRText={{Notices}}<br /> |Section={{Section<br /> |sectionHeading=Next steps<br /> |anchor=next<br /> |alignment=Vertical<br /> |structuredtext=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=DeployIngress}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}<br /> |Status=No<br /> }}<br /> |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=AUTH/Current/AuthPEGuide/ENVMetrics&diff=119904 AUTH/Current/AuthPEGuide/ENVMetrics 2022-05-04T16:42:58Z

<p>Jumunn: </p> <hr /> <div>{{ArticlePEServiceMetrics<br /> |IncludedServiceId=94d22886-7976-4bce-9e98-0400c32c222b<br /> |Annotations=Annotations<br /> |Port=8081<br /> |Endpoint=/prometheus<br /> |MetricsUpdateInterval=Real-time<br /> |MetricsDefined=Yes<br /> |MetricsIntro=Environment Service exposes many Genesys-defined as well as system metrics. You can query Prometheus directly to see all the available metrics. The metrics documented on this page are likely to be particularly useful. Genesys does not commit to maintain other currently available Environment Service metrics not documented on this page.<br /> |PEMetric={{PEMetric<br /> |Metric=api_requests_seconds_count_total<br /> |Type=Counter<br /> |MetricDescription=The total number of API requests to the Environment Service.<br /> }}{{PEMetric<br /> |Metric=api_requests_seconds_sum_total<br /> |Type=Counter<br /> |MetricDescription=The total time of the API requests.<br /> }}{{PEMetric<br /> |Metric=jvm_threads_deadlocked<br /> |Type=Gauge<br /> |MetricDescription=The number of deadlocked threads.<br /> }}{{PEMetric<br /> |Metric=jvm_gc_pause_seconds_count<br /> |Type=Counter<br /> |MetricDescription=How long garbage collection took, in seconds.<br /> }}{{PEMetric<br /> |Metric=gws_responses_total<br /> |Type=Counter<br /> |Label=<br /><br /> <br /> *Code - The response status code.<br /> *Group - The goup of response codes. The values are: 4xx,5xx<br /> |MetricDescription=The number of responses grouped by HTTP code.<br /> }}{{PEMetric<br /> |Metric=jetty_threads_current<br /> |Type=Gauge<br /> |MetricDescription=The current number of Jetty threads.<br /> }}{{PEMetric<br /> |Metric=jvm_memory_used_bytes<br /> |Type=Gauge<br /> |Label=<br /><br /> <br /> *area – The values are "heap" or ”nonheap”.<br /> *id - The values are “G1 Eden Space", "CodeHeap 'non-nmethods'", "G1 Old Gen", "Compressed Class Space", "CodeHeap 'non-profiled nmethods'", "G1 Survivor Space", or "Metaspace".<br /> |MetricDescription=The amount of memory used, in bytes.<br /> }}<br /> |AlertsDefined=No<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=AUTH/Current/AuthPEGuide/Deploy&diff=119125 AUTH/Current/AuthPEGuide/Deploy 2022-04-22T16:35:56Z

<p>Jumunn: Published</p> <hr /> <div>{{ArticlePEServiceDeploy<br /> |ServiceId=6f7f1a8d-4e60-4b8d-a6f0-8cafdbdf0a3e<br /> |IncludeAssumptions=Yes<br /> |Section={{Section<br /> |alignment=Vertical<br /> |structuredtext={{NoteFormat|Make sure to review {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Planning}} for the full list of prerequisites required to deploy Genesys Authentication.|}}<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Prepare your environment<br /> |anchor=Prepare<br /> |alignment=Vertical<br /> |structuredtext=To prepare your environment for the deployment, complete the steps in this section for either OpenShift or Google Kubernetes Engine (GKE).<br /> <br /> ===OpenShift===<br /> Log in to the OpenShift cluster from the host where you will run the deployment:<br /> oc login --token <token> --server <url of api server><br /> First confirm the cluster is running:<br /> <br /> <source lang="text">oc get clusterversion</source><br /> <br /> Create a new project for Genesys Authentication:{{NoteFormat|Deploy Genesys Authentication in the '''gws''' namespace if you use the default OpenShift Ingress Controller; otherwise, deploy in the '''gauth''' namespace.|}}<br /> <br /> <source lang="text">oc new-project gws</source><br /> ===GKE===<br /> Log in to the GKE cluster from the host where you will run the deployment:<br /> <syntaxhighlight><br /> gcloud container clusters get-credentials <cluster><br /> </syntaxhighlight>Create a JSON file called '''create-gauth-namespace.json''' with the following content: <syntaxhighlight><br /> {<br /> "apiVersion": "v1",<br /> "kind": "Namespace",<br /> "metadata": {<br /> "name": "gauth",<br /> "labels": {<br /> "name": "gauth"<br /> }<br /> }<br /> }<br /> </syntaxhighlight>Use the JSON file to create a new namespace for Genesys Authentication:<syntaxhighlight><br /> kubectl apply -f create-gauth-namespace.json<br /> </syntaxhighlight>Now confirm the namespace was created:<syntaxhighlight><br /> kubectl describe namespace gauth<br /> </syntaxhighlight><br /><br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Deploy<br /> |anchor=de<br /> |alignment=Vertical<br /> |structuredtext=To deploy Genesys Authentication, you'll need the Helm package and your overrides file. Copy '''values.yaml''' and the Helm package ('''gauth-<version>.tgz''') to the installation location.<br /> <br /> For OpenShift, select the '''gauth''' project (or '''gws''' if you are using the OpenShift Ingress Controller) you created in {{Link-SomewhereInThisVersion|manual=AuthPEGuide|topic=Deploy|anchor=OpenShift|display text=Prepare your environment}}:<br /> oc project gauth<br /> <br /> For debugging purposes, use the following command to render templates without installing so you can check that resources are created properly:<br /> helm template --debug /gauth-<version>.tgz -f values.yaml<br /> <br /> The result shows Kubernetes descriptors. The values you see are generated from Helm templates, and based on settings from '''values.yaml'''. Ensure that no errors are displayed; you will later apply this configuration to your Kubernetes cluster.<br /> <br /> Now you're ready to deploy Genesys Authentication:<br /> helm install gauth ./gauth-<version>.tgz -f values.yaml -n gauth<br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Configure external access<br /> |anchor=access<br /> |alignment=Vertical<br /> |structuredtext=Follow the instructions for either OpenShift or GKE to make the Genesys Authentication services accessible from outside the cluster.<br /> <br /> ===Create routes in OpenShift===<br /> After deploying, make the Genesys Authentication services accessible from outside the OpenShift cluster using the standard HTTP port. Make sure to use the same hostname for all three routes. Genesys recommends using the following hostname format: <code>gauth.<cluster-subdomain></code>. For example, the VCE cluster (<nowiki>https://console-openshift-console.apps.<yourclusterdomain>.com/</nowiki>) should have the hostname '''gauth.apps.<yourclusterdomain>.com'''<br /> oc create route edge --service=<env-service> --hostname=<hostname> --path /environment<br /> oc create route edge --service=<gauth-service> --hostname=<hostname> --path /auth<br /> oc create route edge --service=<gauth-auth-ui-service> --hostname=<hostname> --path /ui/auth<br /> Verify the new route is created in the '''gauth''' namespace (or '''gws''' if you are using the OpenShift Ingress Controller):<br /> oc get route -n gauth<br /> The result includes the following information about the services:<br /> NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD<br /> env gauth.apps.<yourclusterdomain>.com /environment gauth-environment https None<br /> gauth gauth.apps.<yourclusterdomain>.com /auth gauth-auth https None<br /> gauth-auth-ui gauth.apps.<yourclusterdomain>.com /ui/auth gauth-auth-ui https None<br /> Note: <code>HOST</code> is the host name generated by OpenShift.<br /> <br /> {{AnchorDiv|GKEingress}}<br /> ===Provision ingresses for GKE===<br /> After deploying, make Genesys Authentication services accessible from outside the GKE cluster using the NGINX Ingress Controller. <br /> <br /> Create a YAML file called '''gauth-ingress.yaml''' with the content below. '''Note:''' Replace '''gws.<domain>''' and '''gauth.<domain>''' with your GWS and Genesys Authentication domains, such as <code>gws.test.dev</code>.<syntaxhighlight><br /> apiVersion: extensions/v1beta1<br /> kind: Ingress<br /> metadata:<br /> name: gauth-gws-ingress<br /> namespace: gauth<br /> annotations:<br /> # add an annotation indicating the issuer to use.<br /> cert-manager.io/cluster-issuer: "selfsigned-cluster-issuer"<br /> # Custom annotations for NGINX Ingress Controller<br /> kubernetes.io/ingress.class: "nginx"<br /> nginx.ingress.kubernetes.io/ssl-redirect: "false"<br /> nginx.ingress.kubernetes.io/use-regex: "true"<br /> spec:<br /> rules:<br /> - host: gws.<domain> - e.g. gws.test.dev<br /> http:<br /> paths:<br /> - path: /ui/auth/.*<br /> backend:<br /> serviceName: gauth-auth-ui<br /> servicePort: 80<br /> - path: /auth/.*<br /> backend:<br /> serviceName: gauth-auth<br /> servicePort: 80<br /> - path: /environment/.*<br /> backend:<br /> serviceName: gauth-environment<br /> servicePort: 80<br /> tls:<br /> - hosts:<br /> - gws.<domain> - e.g. gws.test.dev<br /> secretName: gauth-gws-ingress-cert<br /> ---<br /> apiVersion: extensions/v1beta1<br /> kind: Ingress<br /> metadata:<br /> name: gauth-gauth-ingress<br /> namespace: gauth<br /> annotations:<br /> # add an annotation indicating the issuer to use.<br /> cert-manager.io/cluster-issuer: "selfsigned-cluster-issuer"<br /> # Custom annotations for NGINX Ingress Controller<br /> kubernetes.io/ingress.class: "nginx"<br /> nginx.ingress.kubernetes.io/ssl-redirect: "false"<br /> nginx.ingress.kubernetes.io/use-regex: "true"<br /> spec:<br /> rules:<br /> - host: gauth.<domain> - e.g. gauth.test.dev<br /> http:<br /> paths:<br /> - path: /ui/auth/.*<br /> backend:<br /> serviceName: gauth-auth-ui<br /> servicePort: 80<br /> - path: /auth/.*<br /> backend:<br /> serviceName: gauth-auth<br /> servicePort: 80<br /> <br /> - path: /environment/.*<br /> backend:<br /> serviceName: gauth-environment<br /> servicePort: 80<br /> tls:<br /> - hosts:<br /> - gauth.<domain> - e.g. gauth.test.dev<br /> secretName: gauth-gauth-ingress-cert<br /> </syntaxhighlight>Create ingresses with the following command:<syntaxhighlight><br /> kubectl apply -f gauth-ingress.yaml -n gws<br /> </syntaxhighlight><br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Validate the deployment<br /> |alignment=Vertical<br /> |structuredtext=Check the installed Helm release:<br /> helm list<br /> The results should show the Genesys Authentication deployment details. For example:<br /> NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION<br /> gauth gauth 1 2021-05-20 11:56:32.5531685 +0530 +0530 deployed gauth-0.1.77 0.1<br /> Check the '''gauth''' namespace (or '''gws''' if you are using the OpenShift Ingress Controller) status:<br /> helm status gauth<br /> The result should show the namespace details with a status of deployed:<br /> NAME: gauth<br /> LAST DEPLOYED: Thu May 20 11:56:32 2021<br /> NAMESPACE: gauth<br /> STATUS: deployed<br /> REVISION: 1<br /> TEST SUITE: None<br /> Check the Genesys Authentication Kubernetes objects created by Helm:<br /> kubectl get all -n gauth<br /> The result should show all the created pods, service ConfigMaps, and so on.<br /> <br /> Finally, verify that you can now access Genesys Authentication at the following URL: https://<hostname>/ui/auth/sign-in.html<br /> |Status=No<br /> }}<br /> |PEPageType=45d1441f-dc69-4a17-bd47-af5d811ce167<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=GWS/Current/GWSPEGuide&diff=118155 GWS/Current/GWSPEGuide 2022-04-08T19:03:13Z

<p>Jumunn: </p> <hr /> <div>{{MintyDocsManual<br /> |product=Draft:PrivateEdition<br /> |version=Current<br /> |manual=Deployment<br /> |alternateforms=Form:ArticleUnstructured, Form:TaskSummary<br /> |displayname={{MINTYDOCSPRODUCT}} Private Edition Guide<br /> |pagination=no<br /> |Notice=EAP<br /> |ServiceId=11ff3d39-ae2b-4526-b7e5-7dcdf781ef01<br /> |topicslist=* -Overview<br /> ** Overview<br /> ** Architecture<br /> ** HADR<br /> * -Configure and deploy<br /> ** Planning<br /> ** Configure<br /> ** ConfigureTLS<br /> ** Deploy<br /> ** ConfigureIngress<br /> ** DeployIngress<br /> ** Provision<br /> ** ProvisionAS<br /> ** Upgrade<br /> ** UpgradeIngress<br /> * -Operations<br /> ** Metrics<br /> ** Logging<br /> |defaultform=Form:Article<br /> |inherit=no<br /> |Auto=Crafted summary table<br /> |Context=Find links to all the topics in this guide.<br /> |Description=Genesys Web Services and Applications is a service available with the Genesys Multicloud CX private edition offering.<br /> |TSSection={{TSSection<br /> |sectionheading=Overview<br /> |description=Learn more about Genesys Web Services and Applications and how to get started.<br /> |relatedarticles=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Overview}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Architecture}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=HADR}}<br /> }}{{TSSection<br /> |sectionheading=Configure and deploy<br /> |description=Find out how to configure and deploy Genesys Web Services and Applications.<br /> |relatedarticles=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Planning}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureTLS}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=DeployIngress}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ProvisionAS}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Upgrade}}<br /> }}{{TSSection<br /> |sectionheading=Operations<br /> |description=Learn how to monitor Genesys Web Services and Applications with metrics and logging.<br /> |relatedarticles=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Metrics}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Logging}}<br /> }}<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=GWS/Current/GWSPEGuide&diff=118154 GWS/Current/GWSPEGuide 2022-04-08T19:01:45Z

<p>Jumunn: </p> <hr /> <div>{{MintyDocsManual<br /> |product=Draft:PrivateEdition<br /> |version=Current<br /> |manual=Deployment<br /> |alternateforms=Form:ArticleUnstructured, Form:TaskSummary<br /> |displayname={{MINTYDOCSPRODUCT}} Private Edition Guide<br /> |pagination=no<br /> |Notice=EAP<br /> |ServiceId=11ff3d39-ae2b-4526-b7e5-7dcdf781ef01<br /> |topicslist=* -Overview<br /> ** Overview<br /> ** Architecture<br /> ** HADR<br /> * -Configure and deploy<br /> ** Planning<br /> ** Configure<br /> ** ConfigureTLS<br /> ** Deploy<br /> ** ConfigureIngress<br /> ** DeployIngress<br /> ** Provision<br /> ** ProvisionAS<br /> ** Upgrade<br /> ** UpgradeIngress<br /> * -Operations<br /> ** Metrics<br /> ** Logging<br /> |defaultform=Form:Article<br /> |inherit=no<br /> |Auto=Crafted summary table<br /> |Context=Find links to all the topics in this guide.<br /> |Description=Genesys Web Services and Applications is a service available with the Genesys Multicloud CX private edition offering.<br /> |TSSection={{TSSection<br /> |sectionheading=Overview<br /> |description=Learn more about Genesys Web Services and Applications and how to get started.<br /> |relatedarticles=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Overview}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Architecture}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=HADR}}<br /> }}{{TSSection<br /> |sectionheading=Configure and deploy<br /> |description=Find out how to configure and deploy Genesys Web Services and Applications.<br /> |relatedarticles=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Planning}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=DeployIngress}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ProvisionAS}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Upgrade}}<br /> }}{{TSSection<br /> |sectionheading=Operations<br /> |description=Learn how to monitor Genesys Web Services and Applications with metrics and logging.<br /> |relatedarticles=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Metrics}}<br /> *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Logging}}<br /> }}<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=PEC-DC/Current/DCPEGuide/Upgrade&diff=116938 PEC-DC/Current/DCPEGuide/Upgrade 2022-03-30T12:04:26Z

<p>Jumunn: Published</p> <hr /> <div>{{Article<br /> |Standalone=No<br /> |DisplayName=Upgrade, rollback, or uninstall Digital Channels<br /> |TocName=Upgrade, rollback, or uninstall<br /> |Context=Learn how to upgrade, rollback or uninstall Digital Channels.<br /> |ComingSoon=No<br /> |Section={{Section<br /> |sectionHeading=Upgrade Digital Channels<br /> |alignment=Vertical<br /> |structuredtext=Use '''helm upgrade''' to upgrade to a new revision.<br /> <br /> <br /><br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Rollback Digital Channels<br /> |alignment=Vertical<br /> |structuredtext=Use '''helm rollback''' to rollback to the previous revision.<br /> <br /> <br /><br /> |Status=No<br /> }}{{Section<br /> |sectionHeading=Uninstall Digital Channels<br /> |anchor=uninstall<br /> |alignment=Vertical<br /> |structuredtext=Use '''helm delete''' to uninstall the deployment.<br /> |Status=No<br /> }}<br /> |PEPageType=2cad3824-b3b9-43aa-a726-143cc1aaefe2<br /> }}</div>

Jumunn https://all.docs.genesys.com/index.php?title=Form:ThirdPartyItem&diff=116867 Form:ThirdPartyItem 2022-03-29T12:32:05Z

<p>Jumunn: </p> <hr /> <div><noinclude><br /> This is the "ThirdPartyItem" form.<br /> To create a page with this form, enter the page name below;<br /> if a page with that name already exists, you will be sent to a form to edit that page.<br /> <br /> <br /> {{#forminput:form=ThirdPartyItem}}<br /> <br /> </noinclude><includeonly><br /> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div><br /> {{{for template|ThirdPartyItem|multiple|displayed fields when minimized=Name,Version}}}<br /> {{{field|Id|unique|default=uuid|hidden}}}<br /> {| class="formtable"<br /> ! style="width: 30%"| Name: <br /> | style="width: 70%"| {{{field|Name}}}<br /> |-<br /> ! Link:<br /> | {{{field|Link}}}<br /> <br /> |-<br /> ! Version:<br /> | {{{field|Version}}}<br /> |-<br /> ! Service name in OpenShift:<br /> | {{{field|OpenShiftName}}}<br /> |-<br /> ! Service URL in OpenShift:<br /> | {{{field|OpenShiftURL}}}<br /> |-<br /> ! Service name in GKE:<br /> | {{{field|GKEName}}}<br /> |-<br /> ! Service URL in GKE:<br /> | {{{field|GKEURL}}}<br /> |-<br /> ! Purpose of the service:<br /> | {{{field|Purpose|input type=textarea|editor=visualeditor}}}<br /> |-<br /> ! Common across Private Edition?<br /> | {{{field|Common|input type=radiobutton|mandatory|values=Yes,No|default=No}}}<br /> |-<br /> ! Shared service?<br /> | {{{field|Shared|input type=dropdown|existing values only|values=Yes,No,Optional|default=No}}}<br /> |-<br /> ! Mandatory service?<br /> | {{{field|Mandatory|input type=dropdown|existing values only|values=Yes,No,Optional|default=No}}}<br /> |}<br /> <br /> {{{end template}}}<br /> <br /> {{{standard input|summary}}}<br /> <br /> {{{standard input|minor edit}}} {{{standard input|watch}}}<br /> <br /> {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}<br /> </includeonly><br /> {{HideExpandAll}}</div>

Jumunn https://all.docs.genesys.com/index.php?title=File:Pe_auth_architecture.png&diff=116806 File:Pe auth architecture.png 2022-03-25T19:43:49Z

<p>Jumunn: Jumunn uploaded a new version of File:Pe auth architecture.png</p> <hr /> <div></div>

Jumunn https://all.docs.genesys.com/index.php?title=File:Pe_auth_architecture.png&diff=116803 File:Pe auth architecture.png 2022-03-25T19:33:34Z

<p>Jumunn: Jumunn uploaded a new version of File:Pe auth architecture.png</p> <hr /> <div></div>

Jumunn https://all.docs.genesys.com/index.php?title=File:Pe_auth_architecture.png&diff=116802 File:Pe auth architecture.png 2022-03-25T19:31:22Z

<p>Jumunn: Jumunn uploaded a new version of File:Pe auth architecture.png</p> <hr /> <div></div>

Jumunn https://all.docs.genesys.com/index.php?title=File:Pe_gws_architecture.png&diff=116798 File:Pe gws architecture.png 2022-03-25T19:05:06Z

<p>Jumunn: Jumunn uploaded a new version of File:Pe gws architecture.png</p> <hr /> <div></div>

Jumunn https://all.docs.genesys.com/index.php?title=File:Pe_gws_architecture.png&diff=116750 File:Pe gws architecture.png 2022-03-25T00:49:46Z

<p>Jumunn: </p> <hr /> <div></div>

Jumunn https://all.docs.genesys.com/index.php?title=File:Pe_auth_architecture.png&diff=116739 File:Pe auth architecture.png 2022-03-24T14:39:36Z

<p>Jumunn: Jumunn uploaded a new version of File:Pe auth architecture.png</p> <hr /> <div></div>

Jumunn https://all.docs.genesys.com/index.php?title=Template:TrafficTypes&diff=116736 Template:TrafficTypes 2022-03-24T14:09:32Z

<p>Jumunn: Created page with "<noinclude> This is the "TrafficTypes" template. It should be called in the following format: <pre> {{TrafficTypes |Id= |Name= }} </pre> Edit the page to see the template text..."</p> <hr /> <div><noinclude><br /> This is the "TrafficTypes" template.<br /> It should be called in the following format:<br /> <pre><br /> {{TrafficTypes<br /> |Id=<br /> |Name=<br /> }}<br /> </pre><br /> Edit the page to see the template text.<br /> {{#cargo_declare:_table=TrafficTypes|Id=String|Name=String}}<br /> </noinclude><includeonly>{{#cargo_store:_table=TrafficTypes|Id={{{Id|}}}|Name={{{Name|}}} }}<br /> </includeonly><br /> <br /> <br /> <noinclude>[[Category:PrivateEdition]]</noinclude></div>

Jumunn