PEC-REP/Current/GCXIPEGuide/Planning - Revision history

WikiSysop at 18:31, September 7, 2022

2022-09-07T18:31:33Z

WikiSysop at 18:00, April 8, 2022

2022-04-08T18:00:46Z

Show changes

WikiSysop at 19:52, March 30, 2022

2022-03-30T19:52:53Z

Show changes

Tony.gilchrist@genesys.com: Published

2021-11-25T19:45:05Z

Published

Tony.gilchrist@genesys.com at 18:30, October 1, 2021

2021-10-01T18:30:04Z

Tony.gilchrist@genesys.com: Published

2021-09-01T18:29:47Z

Published

Tony.gilchrist@genesys.com: Published

2021-07-13T12:52:29Z

Published

Tony.gilchrist@genesys.com: Published

2021-06-30T17:51:43Z

Published

Tony.gilchrist@genesys.com: Published

2021-06-29T19:46:11Z

Published

New page

{{PEPrerequisites
|DisplayName=Before you begin
|Context=Find out what to do before deploying Genesys Customer Experience Insights (GCXI).
|LimitationsStatus=No
|HelmStatus=No
|HelmText=GCXI containers and Helm chart are available for download in the registry defined in [https://intranet.genesys.com/display/MIC/Docker+Production+Pipeline+and+Registries Docker Production Pipeline and Registries]. You can find the GCXI files in the registry by looking for containers with the name '''gcxi/gcxi''', and Helm charts with the name '''gcxi-$version.'''

'''GCXI Containers'''

*GCXI Helm chart makes use of the following containers.
**'''gcxi''' - main GCXI container, runs as a StatefulSet. This container is roughly 12 GB; ensure that you have enough space to allocate it.
**'''gcxi-control''' - supplementary container, used for GCXI first-install initialization and for cleanup

For information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: {{SuiteLevelLink|helmchart}}

'''GCXI Helm Chart'''
Download the latest yaml files from the repository, or examine the attached files: {{Repository|GCXIyamlExamples.zip|| Sample GCXI yaml files}}
|ThirdPartyStatus=No
|ThirdPartyText=GCXI requires the following services, which are common across the platform:

*Kubernetes 1.17+
*Helm 3.0+
*Postgres 12 RDBMS to handle service databases.

In addition, GCXI requires the following:

*The MicroStrategy server instance that runs in the container includes a temporary pre-activated key, which is required for the operation of MicroStrategy. Request a replacement key from the Genesys Licensing team (or your Genesys Customer Care representative), and apply it once deployment is complete.
*Google Authenticator (GAuth). Alternatively, GCXI includes a native internal login, which you can use to authorize users, instead of GAuth. This document assumes you are using GAuth (the recommended solution), which gives ConfigServer users access to GCXI.

<br />
|StorageStatus=No
|StorageText=GCXI installation requires a set of local Persistent Volumes (PVs). Kubernetes 'local' volumes are simply directories on the host, with specific properties: https://kubernetes.io/docs/concepts/storage/volumes/#local

Example usage:
https://zhimin-wen.medium.com/local-volume-provision-242affd5efe2

Kubernetes provides a powerful volume plugin system that enables Kubernetes workloads to use a wide variety of block and file storage to persist data.

The GCXI Helm chart offers a simples solution that you can use to set up your own PVs, or you can configure PV Dynamic Provisioning in your cluster (so that PVs are created automatically by Kubernetes).

===Volumes Design===
GCXI installation is going to use the following PVC.
{{{!}} class="wikitable" role="grid" resolved
! class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="0" scope="col" role="columnheader" aria-label="Mount Name: No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Mount Name
! class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="1" scope="col" role="columnheader" aria-label="Mount Path(inside container): No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Mount Path

(inside container)
! colspan="1" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="2" scope="col" role="columnheader" aria-label="Description: No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Description
! class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="3" scope="col" role="columnheader" aria-label="Access Type: No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Access Type
! colspan="1" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="4" scope="col" role="columnheader" aria-label="Approx Size: No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Approx Size
! colspan="1" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="5" scope="col" role="columnheader" aria-label="Default Mount Point on Host(may be changed thru values)NB: These dirs MUST pre-exist on your host. That is how the local provisioner works.: No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Default Mount Point on Host

(may be changed thru values)

NB: These dirs MUST pre-exist on your host. That is how the local provisioner works.
! colspan="1" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="6" scope="col" role="columnheader" aria-label="Must be Shared across Nodes?: No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Must be Shared across Nodes?
! colspan="1" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="7" scope="col" role="columnheader" aria-label="Required Node Label(applies to deafult Local PVs setup): No sort applied, activate to apply an ascending sort" tabindex="0" aria-disabled="false" unselectable="on" aria-sort="none"{{!}}Required Node Label

(applies to deafult Local PVs setup)
{{!}}- role="row"
{{!}} class="confluenceTd"{{!}}gcxi-backup
{{!}} class="confluenceTd"{{!}}/genesys/gcxi_shared/backup
{{!}} colspan="1" class="confluenceTd"{{!}}Backups

Used by control container / jobs.
{{!}} class="confluenceTd"{{!}}RWX
{{!}} colspan="1" class="confluenceTd"{{!}}Depends on backup frequency.

5gb+
{{!}} class="confluenceTd"{{!}}/genesys/gcxi/backup

May be overwritten by:

Values.gcxi.local.pv.backup.path
{{!}} colspan="1" class="confluenceTd"{{!}}Only in multiple concurrent installs scenarios.
{{!}} colspan="1" class="confluenceTd"{{!}}gcxi/local-pv-gcxi-backup = "true"
{{!}}- role="row"
{{!}} class="confluenceTd"{{!}}gcxi-log
{{!}} class="confluenceTd"{{!}}/mnt/log
{{!}} colspan="1" class="confluenceTd"{{!}}MSTR logs

Used by main container.

The GCXI Helm chart allows log volumes of legacy <code>hostPath</code> type. This scenario is the default and used in examples below.
{{!}} class="confluenceTd"{{!}}RWX
{{!}} colspan="1" class="confluenceTd"{{!}}Depends on rotation scheme.

5gb+
{{!}} class="confluenceTd"{{!}}/mnt/log/gcxi

subPathExpr: $(POD_NAME)

May be overwritten by:

Values.gcxi.local.pv.log.path
{{!}} colspan="1" class="confluenceTd"{{!}}Not necessarily.
{{!}} colspan="1" class="confluenceTd"{{!}}gcxi/local-pv-gcxi-log = "true"

You don't need node label if you are using hostPath volumes for logs.
{{!}}- role="row"
{{!}} class="confluenceTd"{{!}}gcxi-postgres
{{!}} class="confluenceTd"{{!}}/var/lib/postgresql/data

(if using Postgres in container)

or

disk space in Postgres RDBMS
{{!}} colspan="1" class="confluenceTd"{{!}}Meta DB volume

Used by Postgres container, if deployed.
{{!}} class="confluenceTd"{{!}}RWO
{{!}} colspan="1" class="confluenceTd"{{!}}Depends on usage.

10gb+
{{!}} class="confluenceTd"{{!}}/genesys/gcxi/shared

May be overwritten by:

Values.gcxi.local.pv.postgres.path
{{!}} colspan="1" class="confluenceTd"{{!}}Yes, unless you tie Postgres container to some particular node.
{{!}} colspan="1" class="confluenceTd"{{!}}gcxi/local-pv-postgres-data = "true"
{{!}}- role="row"
{{!}} colspan="1" class="confluenceTd"{{!}}gcxi-share
{{!}} colspan="1" class="confluenceTd"{{!}}/genesys/gcxi_share
{{!}} colspan="1" class="confluenceTd"{{!}}MSTR shared caches and cubes

Used by main container.
{{!}} colspan="1" class="confluenceTd"{{!}}RWX
{{!}} colspan="1" class="confluenceTd"{{!}}Depends on usage.

5gb+
{{!}} class="confluenceTd"{{!}}/genesys/gcxi/data

subPathExpr: $(POD_NAME)

May be overwritten by:

Values.gcxi.local.pv.share.path
{{!}} colspan="1" class="confluenceTd"{{!}}Yes.
{{!}} colspan="1" class="confluenceTd"{{!}}gcxi/local-pv-gcxi-share = "true"<br />
{{!}}}
|NetworkStatus=No
|NetworkText===Ingress==
Session stickiness is desired for better user experience.
Ingress annotations are supported in values.yaml#L317:
<source lang="bash">ingress:
# http path and annotations may be overriden for external and internal access separately
annotations:
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/affinity: cookie
nginx.ingress.kubernetes.io/affinity-mode: persistent
nginx.ingress.kubernetes.io/proxy-body-size: "50m"
nginx.ingress.kubernetes.io/proxy-buffer-size: "8k"
nginx.ingress.kubernetes.io/ssl-redirect: "false"
domain:
external:
annotations:
host:
tls:
enabled: false
secretName:
internal:
annotations:
host:
tls:
enabled: false
secretName:
path: /</source>

Allowlisting is required for GCXI.

==Secrets==
GCXI supports the following ways of secret injection: CSI driver, Kubernetes secrets and Environment Variables.
Secret information is defined in values.yaml#L456:
<source lang="bash">secrets:
- name: gcxi-secret-pg

securityContext:
control:
fsGroup: 500
runAsUser: 500
runAsGroup: 500
worker:
fsGroup: 500
runAsUser: 500
runAsGroup: 500</source>

And in gcxi-worker-statefulset.yaml#L185:
<source lang="bash">- name: gcxi-var
projected:
sources:
- secret:
name: gcxi-secret{{ template "deploymentCode" . }}
optional: true
- secret:
name: gcxi-secret-ext{{ template "deploymentCode" . }}
optional: true
{{- range $secret := .Values.gcxi.secrets }}
- secret:
name: {{ tpl $secret.name $ }}
{{- with $secret.items }}
items:
{{- range $item := $secret.items }}
- key: {{ tpl $item.key $ }}
path: {{ tpl $item.path $ }}
{{- end }}
{{- end }}
optional: true
{{- end }}</source>
==ConfigMaps==
Config map information is defined in gcxi-worker-statefulset.yaml#L94:
<source lang="bash">envFrom:
- configMapRef:
name: gcxi-config{{ template "deploymentCode" . }}
optional: true
- configMapRef:
name: gcxi-config-ext{{ template "deploymentCode" . }}
optional: true
{{- range $cm := .Values.gcxi.configMaps }}
- configMapRef:
name: {{ tpl $cm.name $ }}
optional: true
{{- end }}</source>
==WAF Rules==
WAF rules are defined in variables.tf#L245:
https://github.com/genesysengage/azure-core-ingress/blob/fe25338b20093c76eb2e3ed26fe096442d65e1ae/terraform/dev/westus2/variables.tf#L245

==Pod Security Policy==
GCXI is powered by MicroStrategy software, and as a result has the following requirements/characteristics:

*Very large main container (about 12 GB).
*Openshift-specific 'arbitrary user id' requirement cannot be met, because it requires anyuid SCC.
*The following hostIPC configuration is required on the nodes:
*:<source lang="bash">echo "kernel.sem = 250 1024000 250 4096" >> /etc/sysctl.conf
echo "vm.max_map_count = 5242880" >> /etc/sysctl.conf
sysctl -p</source>
*The following hostIPC configuration is required in most scenarios:
*:<source lang="bash">hostIPC: true
</source>

==SMTP==
The environment variable <code>EMAIL_SERVER</code> is supported by the GCXI container and Helm chart.

==TLS==
The GCXI container does not serve TLS natively. Your environment should be configured to use proxy with HTTPS offload.
|BrowserStatus=No
|BrowserText=MicroStrategy Web is the user interface most often used for accessing, managing, and running the Genesys CX Insights reports. MicroStrategy Web certifies the latest versions, at the time of release, for the following web browsers:

*Apple Safari
*Google Chrome (Windows and iOS)
*Microsoft Edge
*Microsoft Internet Explorer (Versions 9 and 10 are supported, but are not certified)
*Mozilla Firefox

To view updated information about supported browsers, see the [https://www2.microstrategy.com/producthelp/Current/Readme/en-us/content/home.htm MicroStrategy ReadMe].

<br />
|SectionBrowser={{SectionBrowser
|Browser=a1c5ae9e-3ec5-450a-8518-2ee52f956d3f
}}{{SectionBrowser
|Browser=a19c4594-2cac-422e-9f58-0123de3fa7c8
}}{{SectionBrowser
|Browser=4f7728b3-945a-440d-8003-5a2f4043240c
}}
|DependenciesStatus=No
|DependenciesText=GCXI requires the following services:

*Reporting and Analytics Aggregates (RAA) is required to aggregate Genesys Info Mart data.
*Genesys Info Mart and / or Intelligent Workload Distribution (IWD) Data Mart. GCXI can run without these services, but cannot produce meaningful output without them.
*GWS Auth/Environment service
*GWS client id/client secret
|GDPRStatus=No
|GDPRText=GCXI can store Personal Identifiable Information (PII) in logs, history files, and in reports (in scenarios where customers include PII data in reports). Genesys recommends that you do not capture PII in reports, however, if you do so, it is your responsibility to remove any such report data within 21 days or less, if required by General Data Protection Regulation (GDPR) standards.

For more information and relevant procedures, see: {{Link-SomewhereInThisVersion|manual=Administrator|topic=GDPR-GCXI|display text=Genesys CX Insights Support for GDPR}} and the suite-level {{SuiteLevelLink|gdpr}} documentation.
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
}}

@@ Line 4: / Line 4: @@
 |LimitationsStatus=No
 |LimitationsText=GCXI can provide meaningful reports only if {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=GIMPEGuide|display text=Genesys Info Mart}} and {{Link-SomewhereInThisVersion|manual=GCXIPEGuide|topic=PlanningRAA|display text=Reporting and Analytics Aggregates}} (RAA) are deployed and available. Deploy GCXI only after Genesys Info Mart and RAA.
 |HelmStatus=No
 |HelmText=For more information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: {{SuiteLevelLink|helmchart}}
@@ Line 15: / Line 14: @@
 *GCXI Helm chart uses the following containers.
 **'''gcxi''' - main GCXI container, runs as a StatefulSet. This container is roughly 12 GB; ensure that you have enough space to allocate it.
-**'''gcxi-control''' - supplementary container, used for initial installation of GCXI, and for clean up.
+**'''gcxi-control''' - supplementary container, used for initial installation of GCXI, and for clean-up.
 '''GCXI Helm Chart'''
@@ Line 45: / Line 44: @@
 Kubernetes provides a powerful volume plugin system, which enables Kubernetes workloads to use a wide variety of block and file storage to persist data.
-You can use the GCXI Helm chart to easily set up your own PVs, or you can configure PV Dynamic Provisioning in your cluster so that Kubernetes automatically creates PVs.
+You can use the GCXI Helm chart to set up your own PVs, or you can configure PV Dynamic Provisioning in your cluster so that Kubernetes automatically creates PVs.
 ===Volumes Design===
@@ Line 152: / Line 151: @@
 To prepare your environment, complete the following steps:
 #To log in to the cluster, run the following command:
-#:<source lang="bash">oc login --token <token> --server <url of api server></source>
+#*For AKS:
-#To check the cluster version on OpenShift deployments, run the following command:
+#*:<source lang="bash">az aks get-credentials --resource-group <resource group name> --name <cluster name></source>
-#:<source lang="bash">oc get clusterversion</source>
+#*For GKE:
 #To create a new project, run the following command:
-#:OpenShift: <source lang="bash">oc new-project gcxi</source>
+#:GKE or AKS:
 ##Edit the '''create-gcxi-namespace.json''', adding the following values:
 ##:<source lang="bash">{
@@ Line 174: / Line 175: @@
 ##To apply the changes, run the following command:
 ##:<source lang="bash">kubectl apply -f apply create-gcxi-namespace.json</source>
-#For GKE, to confirm namespace creation, run the following command:
+#:OpenShift: <source lang="bash">oc new-project gcxi</source>
 #:<source lang="bash">kubectl describe namespace gcxi</source>
 #Create a secret for docker-registry to pull images from the Genesys JFrog repository:

@@ Line 3: / Line 3: @@
 |Context=Find out what to do before deploying Genesys Customer Experience Insights (GCXI).
 |LimitationsStatus=No
-|LimitationsText=GCXI can provide meaningful reports only if [[Draft:PEC-REP/Current/GIMPEGuide|Genesys Info Mart]] and {{Link-SomewhereInThisVersion|manual=GCXIPEGuide|topic=PlanningRAA|display text=Reporting and Analytics Aggregates}} (RAA) are deployed and available; deploy GCXI only after Genesys Info Mart and RAA.
+|LimitationsText=GCXI can provide meaningful reports only if {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=GIMPEGuide|display text=Genesys Info Mart}} and {{Link-SomewhereInThisVersion|manual=GCXIPEGuide|topic=PlanningRAA|display text=Reporting and Analytics Aggregates}} (RAA) are deployed and available; deploy GCXI only after Genesys Info Mart and RAA.
 |HelmStatus=No
 |HelmText=For information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: {{SuiteLevelLink|helmchart}}
@@ Line 213: / Line 213: @@
 ==WAF Rules==
-WAF rules are defined in the '''variables.tf''' file (see line 245):
+WAF rules are defined in the '''variables.tf''' file (see line 245).
-https://github.com/genesysengage/azure-core-ingress/blob/fe25338b20093c76eb2e3ed26fe096442d65e1ae/terraform/dev/westus2/variables.tf#L245
+<!--https://github.com/genesysengage/azure-core-ingress/blob/fe25338b20093c76eb2e3ed26fe096442d65e1ae/terraform/dev/westus2/variables.tf#L245-->
 ==Pod Security Policy==

@@ Line 19: / Line 19: @@
 Download the latest yaml files from the repository, or examine the attached files: {{Repository|GCXIyamlExamples.zip|| Sample GCXI yaml files}}
 |ThirdPartyStatus=No
-|ThirdPartyText=GCXI requires the following services, which are common across the platform:
+|ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, including Kubernetes, Helm, and other prerequisites, see {{SuiteLevelLink|softwarereq}}.
-*Kubernetes 1.17+
+In addition to common prerequisites, GCXI requires the following:
 *The MicroStrategy server instance that runs in the container includes a temporary pre-activated key, which is required for the operation of MicroStrategy. Request a replacement key from the Genesys Licensing team (or your Genesys Customer Care representative), and apply it once deployment is complete.
 <br />
 |StorageStatus=No
 |StorageText=GCXI installation requires a set of local Persistent Volumes (PVs). Kubernetes 'local' volumes are simply directories on the host, with specific properties: https://kubernetes.io/docs/concepts/storage/volumes/#local
@@ Line 259: / Line 258: @@
 *Genesys Info Mart and / or Intelligent Workload Distribution (IWD) Data Mart. GCXI can run without these services, but cannot produce meaningful output without them.
 *GWS Auth/Environment service
 *GWS client id/client secret
 |GDPRStatus=No

@@ Line 1: / Line 1: @@
 {{PEPrerequisites
-|DisplayName=Before you begin
+|DisplayName=Before you begin deploying GCXI
 |Context=Find out what to do before deploying Genesys Customer Experience Insights (GCXI).
 |LimitationsStatus=No
 |HelmStatus=No
 |HelmText=For information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: {{SuiteLevelLink|helmchart}}
@@ Line 8: / Line 9: @@
 To learn what Helm chart version you must download for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GCXIHelm|display text=Helm charts and containers for Genesys Customer Experience Insights}}
-GCXI containers and Helm chart are available for download in the registry defined in [https://intranet.genesys.com/display/MIC/Docker+Production+Pipeline+and+Registries Docker Production Pipeline and Registries]. You can find the GCXI files in the registry by looking for containers with the name '''gcxi/gcxi''', and Helm charts with the name '''gcxi-$version.'''
+<!--GCXI containers and Helm chart are available for download in the registry defined in [https://intranet.genesys.com/display/MIC/Docker+Production+Pipeline+and+Registries Docker Production Pipeline and Registries]. You can find the GCXI files in the registry by looking for containers with the name '''gcxi/gcxi''', and Helm charts with the name '''gcxi-$version.'''-->
 '''GCXI Containers'''
@@ Line 39: / Line 39: @@
 Kubernetes provides a powerful volume plugin system that enables Kubernetes workloads to use a wide variety of block and file storage to persist data.
-The GCXI Helm chart offers a simples solution that you can use to set up your own PVs, or you can configure PV Dynamic Provisioning in your cluster (so that PVs are created automatically by Kubernetes).
+The GCXI Helm chart offers a simple solution that you can use to set up your own PVs, or you can configure PV Dynamic Provisioning in your cluster (so that PVs are created automatically by Kubernetes).
 ===Volumes Design===
@@ Line 146: / Line 146: @@
 |NetworkText===Ingress==
 Session stickiness is desired for better user experience.
-Ingress annotations are supported in values.yaml#L317:
+Ingress annotations are supported in the '''values.yaml''' file (see line 317):
 <source lang="bash">ingress:
      # http path and annotations may be overriden for external and internal access separately
@@ Line 175: / Line 175: @@
 ==Secrets==
 GCXI supports the following ways of secret injection: CSI driver, Kubernetes secrets and Environment Variables.
-Secret information is defined in values.yaml#L456:
+Secret information is defined in the '''values.yaml''' file (see line 456), and in the '''gcxi-worker-statefulset.yaml''' file (see line 185):
 <source lang="bash">- name: gcxi-var
          projected:
@@ Line 212: / Line 198: @@
            {{- end }}</source>
 ==ConfigMaps==
-Config map information is defined in gcxi-worker-statefulset.yaml#L94:
+Config map information is defined in the '''gcxi-worker-statefulset.yaml''' file (see line 94):
 <source lang="bash">envFrom:
          - configMapRef:
@@ Line 225: / Line 211: @@
              optional: true
          {{- end }}</source>
 ==WAF Rules==
-WAF rules are defined in variables.tf#L245:
+WAF rules are defined in the '''variables.tf''' file (see line 245):
 https://github.com/genesysengage/azure-core-ingress/blob/fe25338b20093c76eb2e3ed26fe096442d65e1ae/terraform/dev/westus2/variables.tf#L245
@@ Line 233: / Line 220: @@
 *Very large main container (about 12 GB).
-*Openshift-specific 'arbitrary user id' requirement cannot be met, because it requires anyuid SCC.
+*An arbitrary user ID (UID) and group ID is assigned to pods during deployment (file ownership is assigned as genesys:root (500:0)). For information about configuring arbitrary UID, see {{Link-SomewhereInThisVersion|manual=GCXIPEGuide|topic=Configure|display text=Configure security}}.
 *The following hostIPC configuration is required on the nodes:
 *:<source lang="bash">echo "kernel.sem = 250 1024000 250 4096" >> /etc/sysctl.conf

@@ Line 26: / Line 26: @@
 *The MicroStrategy server instance that runs in the container includes a temporary pre-activated key, which is required for the operation of MicroStrategy. Request a replacement key from the Genesys Licensing team (or your Genesys Customer Care representative), and apply it once deployment is complete.
-*Google Authenticator (GAuth). Alternatively, GCXI includes a native internal login, which you can use to authorize users, instead of GAuth. This document assumes you are using GAuth (the recommended solution), which gives ConfigServer users access to GCXI.
+*Genesys Platform Authentication thru Config Server (GAuth). Alternatively, GCXI includes a native internal login, which you can use to authorize users, instead of GAuth. This document assumes you are using GAuth (the recommended solution), which gives ConfigServer users access to GCXI.
 <br />