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

WikiSysop at 17:30, April 8, 2022

2022-04-08T17:30:41Z

Tgilchri: Published

2022-03-25T12:01:54Z

Published

Tony.gilchrist@genesys.com: Published

2021-09-01T18:29:56Z

Published

Tony.gilchrist@genesys.com: Published

2021-06-30T17:51:42Z

Published

Tony.gilchrist@genesys.com: Published

2021-06-29T19:46:15Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Configure GCXI
|Context=Learn how to configure Genesys Customer Experience Insights (GCXI).
|ComingSoon=No
|Section={{Section
|sectionHeading=Override Helm chart values
|alignment=Vertical
|structuredtext=Before you begin, download the latest yaml files from the repository, or examine the attached files: {{Repository|GCXIyamlExamples.zip|| Sample GCXI yaml files}}. Helm values are described in '''values.yaml'''. See the comments accompanying each Helm value.

You can override values in the Helm charts to configure Private Edition. For more information, see the "suite-level" documentation about how to override Helm chart values: {{SuiteLevelLink|helmoverride}}.

|Status=No
}}{{Section
|sectionHeading=Configure Kubernetes
|alignment=Vertical
|structuredtext=This section provides information about Kubernetes configuration.
==ConfigMaps==
Configuration information is stored in ConfigMap.

See the '''gcxi-worker-statefulset.yaml''' file:
<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</source>

==Secrets==
GCXI supports the following methods of secret injection:

*CSI driver
*Kubernetes secrets
*Environment Variables

See the '''values.yaml''' file:
<source lang="bash">secrets:
- name: gcxi-secret-pg</source>

See the '''gcxi-worker-statefulset.yaml''' file:
<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>
|Status=No
}}{{Section
|sectionHeading=Configure security
|alignment=Vertical
|structuredtext=GCXI is based on a 3rd-party product (MicroStrategy), and as result has some special considerations:

*The main container is about 12 GB.
*The Openshift-specific <nowiki>''</nowiki>arbitrary user id<nowiki>''</nowiki> requirement cannot be satisfied. GCXI requires anyuid SCC.
*GCXI requires specific hostIPC configuration 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>
*In most deployments, GCXI requires that hostIPC be set:
*:<source lang="bash">hostIPC: true</source>
|Status=No
}}
|PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97
}}

@@ Line 24: / Line 24: @@
 {{!}}}
 -->
 |Status=No
 }}{{Section
@@ Line 85: / Line 84: @@
 |structuredtext=GCXI is based on a 3rd-party product (MicroStrategy), and as result has some special considerations:
 {{AnchorDiv|hostIPC}}
 *The main container is about 12 GB.
-*Genesys recommends that you enable hostIPC, However, hostIPC is disabled by default and in some deployments, GCXI can operate successfully without enabling it.
+*Genesys recommends that you enable hostIPC. However, hostIPC is disabled by default and in some deployments, GCXI can operate successfully without it.
-**Enable it by setting:
+*#Enable hostIPC by setting:
-**:<source lang="bash">hostIPC: true</source>
+*#:<source lang="bash">hostIPC: true</source>
-**Configure hostIPC at the node level as follows:
+*#Configure hostIPC at the node level as follows:
-**:<source lang="bash">echo "kernel.sem = 250 1024000 250 4096" >> /etc/sysctl.conf
+*#:<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>
 ===Arbitrary UID===
-*An arbitrary user ID (UID) and group ID is assigned to pods during deployment (file ownership is assigned as genesys:root (500:0)).
 *If your OpenShift deployment uses arbitrary UIDs, you must override the securityContext settings in the '''values.yaml''' file (see line 456) as follows:
-*: <source lang="text">secrets:
+*:<source lang="text">secrets:
   podSecurityContext:
     fsGroup: null

@@ Line 84: / Line 84: @@
 |alignment=Vertical
 |structuredtext=GCXI is based on a 3rd-party product (MicroStrategy), and as result has some special considerations:
+{{AnchorDiv|hostIPC}}
 *The main container is about 12 GB.
-*GCXI requires specific hostIPC configuration at the node level:
+*Genesys recommends that you enable hostIPC, However, hostIPC is disabled by default and in some deployments, GCXI can operate successfully without enabling it.
-*:<source lang="bash">echo "kernel.sem = 250 1024000 250 4096" >> /etc/sysctl.conf
+**Enable it by setting:
 echo "vm.max_map_count = 5242880" >> /etc/sysctl.conf
 sysctl -p</source>
-*In most deployments, GCXI requires that hostIPC be set:
 ===Arbitrary UID===
 *An arbitrary user ID (UID) and group ID is assigned to pods during deployment (file ownership is assigned as genesys:root (500:0)).
 *If your OpenShift deployment uses arbitrary UIDs, you must override the securityContext settings in the '''values.yaml''' file (see line 456) as follows:
 *: <source lang="text">secrets:
-  securityContext:
+ podSecurityContext:
-    control:
+   fsGroup: null
-      fsGroup: null
+   runAsUser: null
-      runAsUser: null
+   runAsGroup: 0
-      runAsGroup: null
+   runAsNonRoot: true
-    worker:
-      fsGroup: null
+ securityContext:
-      runAsUser: null
+   fsGroup: null
-      runAsGroup: null</source>
+   runAsUser: null
 *:The default values (user ID = 500) are suitable for many other deployment scenarios:
 *:<source lang="text">secrets: