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

WikiSysop at 16:01, March 29, 2023

2023-03-29T16:01:44Z

WikiSysop at 18:46, September 7, 2022

2022-09-07T18:46:23Z

Show changes

WikiSysop at 17:15, April 11, 2022

2022-04-11T17:15:40Z

WikiSysop at 19:53, March 30, 2022

2022-03-30T19:53:47Z

Show changes

Tony.gilchrist@genesys.com: Published

2021-12-06T18:55:03Z

Published

Tony.gilchrist@genesys.com: Published

2021-11-01T19:51:21Z

Published

Show changes

Olena.chapovska@genesys.com: Published

2021-07-01T05:43:05Z

Published

Olena.chapovska@genesys.com: Published

2021-07-01T01:09:46Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Shared Provisioning
|Context=Learn how to configure Genesys Pulse.
|ComingSoon=No
|Section={{Section
|sectionHeading=Prerequisites
|alignment=Vertical
|structuredtext=Please complete {{Link-SomewhereInThisVersion|manual=PulsePEGuide|topic=Planning}} instructions.

Information you will need:

*Versions:
**<image-version> = 9.0.100.10
**<chart-versions>= 9.0.100+10
*K8S namespace <namespace> (e.g. 'pulse')
*Project Name <project-name> (e.g. 'pulse')
*Postgres credentials
**<db-host>
**<db-port>
**<db-port-internal>
**<db-name>
**<db-user>
**<db-user-password>
**<db-superuser>
**<db-superuser-password>
**<db-ssl-mode>
*Docker credentials
**<docker-email>
**<docker-password>
**<docker-user>
*OpenShift credentials
**<openshift-url>
**<openshift-port>
**<openshift-token>
*Redis credentials
**<redis-host>
**<redis-port>
**<redis-password>
**<redis-enable-ssl>
*Tenant service variables
**<tenant-uuid>
**<tenant-sid>
**<tenant-name>
*GAuth/GWS service variables
**<gauth-url-external>
**<gauth-url-internal>
**<gauth-client-id>
**<gauth-client-secret>
**<gws-url-external>
**<gws-url-internal>

Fill appropriate placeholders and save values in <tt>.shared_init_variables</tt>:<source lang="text">export CHART_VERSION='<chart-version>'
export DB_HOST='<db-host>'
export DB_NAME_SHARED='<db-name>'
export DB_NAME_SUPERUSER='<db-superuser>'
export DB_PASSWORD_SHARED='<db-user-password>'
export DB_PASSWORD_SUPERUSER='<db-superuser-password>'
export DB_PORT='<db-port>'
export DB_SSL_MODE='<db-ssl-mode>'
export DB_USER_SHARED='<db-user>'
export DOCKER_EMAIL='<docker-email>'
export DOCKER_PASSWORD='<docker-password>'
export DOCKER_REGISTRY='<docker-registry>'
export DOCKER_REGISTRY_SECRET_NAME='<docker-registry-secret-name>'
export DOCKER_TAG='<image-version>'
export DOCKER_USER='<docker-user>'
export GAUTH_CLIENT_ID='<gauth-client-id>'
export GAUTH_CLIENT_SECRET='<gauth-client-secret>'
export GAUTH_URL='<gauth-url-external>'
export GAUTH_URL_INTERNAL='<gauth-url-internal>'
export GWS_URL='<gws-url-external>'
export GWS_URL_INTERNAL='<gws-url-internal>'
export NAMESPACE='<namespace>'
export OS_ADD_SCC_TO_USER='<scc-user>'
export OS_PORT='<openshift-port>'
export OS_TOKEN='<openshift-token>'
export OS_URL='<openshift-url>'
export PROJECT_NAME='<project-name>'
export PULSE_ENDPOINT='<pulse-endpoint>'
export PULSE_HEALTH_PORT=8090
export PV_STORAGE_CLASS_RW_MANY='<rw-many-storage-class>'
export REDIS_ENABLE_SSL='<redis-enable-ssl>'
export REDIS_HOST='<redis-host>'
export REDIS_PASSWORD='<redis-password>'
export REDIS_PORT='<redis-port>'
export TENANT_UUID='<tenant-uuid>'
export TENANT_DCU='2'
export TENANT_NAME='<tenant-name>'
export TENANT_SID='<tenant-sid>'</source><br />
|Status=No
}}{{Section
|sectionHeading=Create project in OpenShift
|alignment=Vertical
|structuredtext='''Login using token'''
<source lang="text">source .shared_init_variables

oc login --token="${OS_TOKEN}" \
--server="${OS_URL}:${OS_PORT}" \
--insecure-skip-tls-verify=true</source>

'''Create project'''
<source lang="text">source .shared_init_variables

oc new-project "${PROJECT_NAME}" \
--description="${PROJECT_NAME}" \
--display-name="${PROJECT_NAME}" </source>

'''Add SCC to user'''
<source lang="text">source .shared_init_variables

oc adm policy add-scc-to-user "${OS_ADD_SCC_TO_USER}" -z default -n "${NAMESPACE}"</source>

'''Enable namespace'''
<source lang="text">source .shared_init_variables

oc annotate namespace --overwrite "${NAMESPACE}" 'scheduler.alpha.kubernetes.io/defaultTolerations'='[{"operator": "Equal", "effect": "NoSchedule", "key": "team", "value": "pat"}]'</source>

'''Switch to project'''
<source lang="text">
source .shared_init_variables

oc project "${PROJECT_NAME}" </source>

'''Create secret for auth to registry'''
<source lang="text">
source .shared_init_variables

oc create secret docker-registry "${DOCKER_REGISTRY_SECRET_NAME}" \
--docker-server="${DOCKER_REGISTRY}" \
--docker-username="${DOCKER_USER}" \
--docker-password="${DOCKER_PASSWORD}" \
--docker-email="${DOCKER_EMAIL}"

oc secrets link default "${DOCKER_REGISTRY_SECRET_NAME}" --for=pull </source>
|Status=No
}}{{Section
|sectionHeading=PostgreSQL
|alignment=Vertical
|structuredtext='''Create shared db user'''

As PosgreQSL superuser save the following as <tt>create_shared_db_role.sql:</tt><source lang="text">CREATE ROLE "${DB_USER_SHARED}@${DB_HOST}" WITH NOSUPERUSER LOGIN ENCRYPTED PASSWORD '${DB_PASSWORD_SHARED}';</source>
Run:
<source lang="text">source .shared_init_variables

envsubst < ./create_shared_db_role.sql | \
PGPASSWORD=${DB_PASSWORD_SUPERUSER} psql -h "${DB_HOST}" -p "${DB_PORT}" -U "${DB_NAME_SUPERUSER}" -f - </source>

'''Create shared db and grant privileges'''

Save the following as <tt>create_shared_db.sql</tt>
<source lang="text">CREATE DATABASE ${DB_NAME_SHARED};
GRANT ALL PRIVILEGES ON DATABASE ${DB_NAME_SHARED} TO "${DB_USER_SHARED}@${DB_HOST}"; </source>
Run:
<source lang="text">source .shared_init_variables

envsubst < ./create_shared_db.sql | \
PGPASSWORD=${DB_PASSWORD_SUPERUSER} psql -h "${DB_HOST}" -p "${DB_PORT}" -U "${DB_NAME_SUPERUSER}" -f -</source>
|Status=No
}}{{Section
|sectionHeading=Deployment
|alignment=Vertical
|structuredtext====Preparations===
'''Create pulse-postgres-configmap'''

Save as <tt>pulse-postgres-configmap</tt>.yaml:<source lang="text">
apiVersion: v1
kind: ConfigMap
metadata:
name: pulse-postgres-configmap
namespace: ${NAMESPACE}
data:
META_DB_HOST: '${DB_HOST}'
META_DB_PORT: '${DB_PORT}'
META_DB_SSL_MODE: '${DB_SSL_MODE}' </source>

Run:<source lang="text">source .shared_init_variables

envsubst < ./pulse-postgres-configmap | \
oc apply --namespace=${NAMESPACE} \
-f - </source>

'''Validate pulse-postgres-configmap'''

The following command should return created ConfigMap:<source lang="text">source .shared_init_variables

oc get configmap pulse-postgres-configmap -n=${NAMESPACE} </source>

Example:<source lang="text">
NAME DATA AGE
pulse-postgres-configmap 3 5h5m </source>

'''Create pulse-redis-configmap'''

Save as <tt>pulse-redis-configmap:</tt><source lang="text">apiVersion: v1
kind: ConfigMap
metadata:
name: pulse-redis-configmap
namespace: ${NAMESPACE}
data:
REDIS_HOST: '${REDIS_HOST}'
REDIS_PORT: '${REDIS_PORT}'
REDIS_ENABLE_SSL: '${REDIS_ENABLE_SSL}' </source>

Run:<source lang="text">
source .shared_init_variables

envsubst < ./pulse-redis-configmap | \
oc apply --namespace=${NAMESPACE} \
-f - </source>

'''Validate pulse-redis-configmap'''

The following command should return created ConfigMap:<source lang="text">source .shared_init_variables

oc get configmap pulse-redis-configmap -n=${NAMESPACE} </source>

Example:<source lang="text">NAME DATA AGE
pulse-redis-configmap 3 4h38m </source>

'''Create pulse-gws-secret'''

Save as <tt>pulse-gws-secret.yaml:</tt><source lang="text">
apiVersion: v1
kind: Secret
metadata:
name: pulse-gws-secret
namespace: ${NAMESPACE}
type: Opaque
stringData:
clientId: ${GAUTH_CLIENT_ID}
clientSecret: ${GAUTH_CLIENT_SECRET} </source>

Run:<source lang="text">source .shared_init_variables

envsubst < ./pulse-gws-secret.yaml | \
oc apply --namespace=${NAMESPACE} \
-f - </source>

'''Validate pulse-gws-secret'''
The following command should return created secret:<source lang="text">source .shared_init_variables

oc get secret pulse-gws-secret -n=${NAMESPACE} </source>

Example:<source lang="text">
NAME TYPE DATA AGE
pulse-gws-secret Opaque 2 5h4m </source>

'''Create pulse-postgres-secret'''

Save as <tt>pulse-postgres-secret.yaml:</tt><source lang="text">apiVersion: v1
kind: Secret
metadata:
name: pulse-postgres-secret
namespace: ${NAMESPACE}
type: Opaque
stringData:
META_DB_ADMIN: '${DB_USER_SHARED}'
META_DB_ADMINPWD: '${DB_PASSWORD_SHARED}' </source>

Run:<source lang="text">source .shared_init_variables

envsubst < ./pulse-postgres-secret.yaml | \
oc apply --namespace=${NAMESPACE} \
-f - </source>

'''Validate pulse-postgres-secret'''

The following command should return created secret:<source lang="text">source .shared_init_variables

oc get secret pulse-postgres-secret -n=${NAMESPACE} </source>

Example:<source lang="text">NAME TYPE DATA AGE
pulse-postgres-secret Opaque 2 5h30m </source>

'''Create pulse-redis-secret'''

Save as <tt>pulse-redis-secret.yaml</tt>:<source lang="text">apiVersion: v1
kind: Secret
metadata:
name: pulse-redis-secret
namespace: ${NAMESPACE}
type: Opaque
stringData:
REDIS01_KEY: ${REDIS_PASWORD} </source>

Run:<source lang="text">source .shared_init_variables

envsubst < ./pulse-redis-secret.yaml | \
oc apply --namespace=${NAMESPACE} \
-f - </source>

'''Validate pulse-redis-secret'''

The following command should return created secret:<source lang="text">
source .shared_init_variables

oc get secret pulse-redis-secret -n=${NAMESPACE} </source>

Example:<source lang="text">
NAME TYPE DATA AGE
pulse-redis-secret Opaque 1 5h5m </source>

===Install init helm chart===
Use this chart for shared Postgres database.

'''Get init helm chart''' <source lang="text">helm repo update
helm search repo pe-jfrog-stage/init </source>

'''Prepare override file'''

Save as <tt>values-override-init.yaml:</tt><source lang="text"># Default values for init.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

image:
name: init
tag: "${DOCKER_TAG}"
pullPolicy: IfNotPresent
repository: "${DOCKER_REGISTRY}/pulse/"

imagePullSecrets: [name: ${DOCKER_REGISTRY_SECRET_NAME}]

# tenant identification, or empty for shared deployment
tenants:
- id: "${TENANT_UUID}"
name: "${TENANT_NAME}"
key: "${TENANT_SID}"
dcu: "${TENANT_DCU}"

# common configuration.
config:
dbName: "${DB_NAME_SHARED}"
# set "true" when need @host added for username
dbUserWithHost: true
# set "true" for CSI secrets
mountSecrets: false
# Postgres config map name
postgresConfig: "pulse-postgres-configmap"
# Postgres secret name
postgresSecret: "pulse-postgres-secret"
# Postgres secret key for user
postgresSecretUser: "META_DB_ADMIN"
# Postgres secret key for password
postgresSecretPassword: "META_DB_ADMINPWD"

## Service account settings
serviceAccount:
# Specifies whether a service account should be created
create: false
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""

## Add annotations to all pods
##
podAnnotations: {}

## Containers should run as genesys user and cannot use elevated permissions
## !!! THESE OPTIONS SHOULD NOT BE CHANGED UNLESS INSTRUCTED BY GENESYS !!!
# securityContext: {}
# runAsUser: 500
# runAsGroup: 500

## Resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
limits:
memory: 256Mi
cpu: 200m
requests:
memory: 128Mi
cpu: 100m

## Priority Class
## ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
##
priorityClassName: ""

## Node labels for assignment.
## ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector: {}

## Tolerations for assignment.
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: [] </source>

'''Install init helm chart'''

Run: <source lang="text">
source .shared_init_variables

envsubst < ./values-override-init.yaml | \
helm upgrade --install pulse-init pe-jfrog-stage/init \
--wait --wait-for-jobs \
--version="${CHART_VERSION}" \
--namespace="${NAMESPACE}" \
-f - </source>

This command will finish with exit code 0 if installation is successful.

'''Validate init helm chart'''

The following command should report pulse-init job as Completed:<source lang="text">
source .shared_init_variables

oc get pods -n="${NAMESPACE}" -l "app.kubernetes.io/name=init,app.kubernetes.io/instance=pulse-init" </source>

Example:<source lang="text">NAME READY STATUS RESTARTS AGE
pulse-init-job-bvstl 0/1 Completed 0 3h30m </source>

===Install pulse helm chart===
Use this chart for the shared part.

'''Get pulse helm chart''' <source lang="text">helm repo update
helm search repo pe-jfrog-stage/pulse </source>

'''Prepare override file'''

Save as <tt>values-override-pulse.yaml:</tt><source lang="text"># Default values for pulse.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

image:
name: pulse
tag: "${DOCKER_TAG}"
pullPolicy: IfNotPresent
repository: "${DOCKER_REGISTRY}/pulse/"

imagePullSecrets: [name: ${DOCKER_REGISTRY_SECRET_NAME}]

replicaCount: 2

# common configuration.
config:
dbName: "${DB_NAME_SHARED}"
# set "true" when need @host added for username
dbUserWithHost: true
# set "true" for CSI secrets
mountSecrets: false
# Postgres config map name
postgresConfig: "pulse-postgres-configmap"
# Postgres secret name
postgresSecret: "pulse-postgres-secret"
# Postgres secret key for user
postgresSecretUser: "META_DB_ADMIN"
# Postgres secret key for password
postgresSecretPassword: "META_DB_ADMINPWD"
# Redis config map name
redisConfig: "pulse-redis-configmap"
# Redis secret name
redisSecret: "pulse-redis-secret"
# Redis secret key for access key
redisSecretKey: "REDIS01_KEY"
# GAuth secret name
gwsSecret: "pulse-gws-secret"
# GAuth secret key for client_id
gwsSecretClientId: "clientId"
# GAuth secret key for client_secret
gwsSecretClientSecret: "clientSecret"

# monitoring settings
monitoring:
# enable the Prometheus metrics endpoint
enabled: false
# port is <options.managementPort>
# HTTP path is <options.managementContext><options.prometheusEndpoint>
# additional annotations required for monitoring PODs
# you can reference values of other variables as {{.Values.variable.full.name}}
podAnnotations: {}
# prometheus.io/scrape: "true"
# prometheus.io/port: "{{.Values.options.managementPort}}"
# prometheus.io/path: "{{.Values.options.managementContext}}{{.Values.options.prometheusEndpoint}}"
serviceMonitor:
# enables ServiceMonitor creation
enabled: false
# interval at which metrics should be scraped
scrapeInterval: 30s
# timeout after which the scrape is ended
scrapeTimeout:
# namespace of the ServiceMonitor, defaults to the namespace of the service
namespace:
additionalLabels: {}

# common log configuration
log:
# target directory where log will be stored, leave empty for default
logDir: ""
# path where volume will be mounted
volumeMountPath: /data/log
# log volume type: none | hostpath | pvc
volumeType: pvc
# log volume hostpath, used with volumeType "hostpath"
volumeHostPath: /mnt/log
# log PVC parameters, used with volumeType "pvc"
pvc:
name: pulse-logs
accessModes:
- ReadWriteMany
capacity: 10Gi
class: ${PV_STORAGE_CLASS_RW_MANY}

# application options
options:
authUrl: "https://${GAUTH_URL}"
authUrlInt: "http://${GAUTH_URL_INTERNAL}"
gwsUrl: "https://${GWS_URL}"
gwsUrlInt: "http://${GWS_URL_INTERNAL}"

## Service account settings
serviceAccount:
# Specifies whether a service account should be created
create: false
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""

## Add annotations to all pods
##
podAnnotations: {}

## Add labels to all pods
##
podLabels: {}

## Containers should run as genesys user and cannot use elevated permissions
## !!! THESE OPTIONS SHOULD NOT BE CHANGED UNLESS INSTRUCTED BY GENESYS !!!
# securityContext: {}
# runAsUser: 500
# runAsGroup: 500

## Ingress configuration
ingress:
enabled: true
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
## recommended to increase proxy-body-size size
# nginx.ingress.kubernetes.io/proxy-body-size: 5m
hosts:
- host: "${PULSE_ENDPOINT}"
paths: [/]
tls: []
# - secretName: chart-example-tls
# hosts:
# - chart-example.local

gateway:
enabled: false

## Resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
limits:
memory: 4Gi
cpu: 1
requests:
memory: 650Mi
cpu: 100m

## HPA Settings
## Not supported in this release!
hpa:
enabled: false

## Priority Class
## ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
##
priorityClassName: ""

## Node labels for assignment.
## ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector: {}

## Tolerations for assignment.
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []

## Pod Disruption Budget Settings
podDisruptionBudget:
enabled: false

## Affinity for assignment.
## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
##
affinity: {}

# control network policies
networkPolicies:
enabled: false </source>

'''Install pulse helm chart'''

Run:<source lang="text">source .shared_init_variables

envsubst < ./values-override-pulse.yaml | \
helm upgrade --install pulse pe-jfrog-stage/pulse \
--wait \
--version="${CHART_VERSION}" \
--namespace="${NAMESPACE}" \
-f - </source>

This command will finish with exit code 0 if installation is successful.

'''Validate pulse helm chart'''

The following report running pods: <source lang="text">source .shared_init_variables

oc get pods -n="${NAMESPACE}" -l "app.kubernetes.io/name=pulse,app.kubernetes.io/instance=pulse" </source>

Example:<source lang="text">NAME READY STATUS RESTARTS AGE
pulse-5dbd484467-bh82r 1/1 Running 0 4h26m
pulse-5dbd484467-wz7xt 1/1 Running 0 4h26m </source>
|Status=No
}}{{Section
|sectionHeading=Validation
|alignment=Vertical
|structuredtext='''Check logs for error'''
<source lang="text">oc get pods
os logs <pulse-pod-id> </source>

'''Health validation'''

<tt>GET /actuator/metrics/pulse.health.all</tt>

Run in two different consoles (1 -> 2).

<u>Console 1:</u>
<source lang="text">source .shared_init_variables

export POD_NAME=$(oc get pods --namespace=${NAMESPACE} -l "app.kubernetes.io/name=pulse,app.kubernetes.io/instance=pulse" -o jsonpath="{.items[0].metadata.name}")
oc --namespace=${NAMESPACE} port-forward $POD_NAME ${PULSE_HEALTH_PORT}:${PULSE_HEALTH_PORT} </source>

<u>Console 2:</u>
<source lang="text">source .shared_init_variables

curl -X GET http://127.0.0.1:${PULSE_HEALTH_PORT:-?}/actuator/metrics/pulse.health.all \
-H 'Content-Type: application/json' | jq '.'</source>

Genesys Pulse is successfully running and can connect to Postgres and Redis when:

*HTTP response code is 200
*JSON response is measurements.statistic.value=1<source lang="text">{
"name": "pulse.health.all",
"description": "Provides overall application status",
"baseUnit": "Boolean",
"measurements": [
{
"statistic": "VALUE",
"value": 1
}
],
"availableTags": [
{
"tag": "deployment.code",
"values": [
"pulse"
]
},
{
"tag": "application.name",
"values": [
"pulse"
]
}
]
}</source>
|Status=No
}}{{Section
|sectionHeading=Troubleshooting
|alignment=Vertical
|structuredtext='''Check init helm manifests'''

Run to output manifest into helm-template directory:

<source lang="text">source .shared_init_variables

envsubst < ./values-override-init.yaml | \
helm template \
--version="${CHART_VERSION}" \
--namespace="${NAMESPACE}" \
--debug \
--output-dir helm-template \
init pe-jfrog-stage/init \
-f -</source>

'''Check pulse helm manifests'''

Run to output manifest into helm-template directory:

<source lang="text">source .shared_init_variables

envsubst < ./values-override-pulse.yaml | \
helm template \
--version="${CHART_VERSION}" \
--namespace="${NAMESPACE}" \
--debug \
--output-dir helm-template \
pulse pe-jfrog-stage/pulse \
-f -</source>
|Status=No
}}{{Section
|sectionHeading=Override Helm chart values
|alignment=Vertical
|structuredtext=<div style="background-color: aliceblue; font-style: italic;">Link to the "suite-level" documentation about how to override Helm chart values: {{SuiteLevelLink|helmoverride}} If there are multiple YAML files (for example, one for each container if your service has multiple containers), you could use a table for each file or use a single table with an extra column for the file name. If the parameter is related to a feature documented elsewhere, you can include a link in the Description column. For example, descriptions for logging setting can link to the Logging page.
Note: We are still working on an approach to handle documentation for Helm chart values, so please leave this section until the end.
</div>
{{{!}} class="wikitable"
{{!}}+
!Parameter
!Description
!Default
!Valid values
{{!}}-
{{!}}service.port
{{!}}Designer service to be exposed.
{{!}}8888
{{!}}A valid port.
{{!}}-
{{!}}...
{{!}}
{{!}}
{{!}}
{{!}}}
|Status=Yes
}}{{Section
|sectionHeading=Configure Kubernetes
|alignment=Vertical
|structuredtext=<div style="background-color: aliceblue; font-style: italic;">Document the layouts for the following so customers can create them if their Helm chart doesn't include a way to do this:

*ConfigMaps
*Secrets
</div>
|Status=Yes
}}{{Section
|sectionHeading=Configure security
|alignment=Vertical
|structuredtext=<div style="background-color: aliceblue; font-style: italic;">List security-related settings, such as how to set up credentials and certificates for third-party services.</div>
|Status=Yes
}}
|PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97
}}

@@ Line 92: / Line 92: @@
 <source lang="bash">helm repo update
 helm search repo pulsehelmrepo/init</source>
-====Prepare override-init file (GKE and OpenShift)====
+====Prepare override-init file (GKE)====
 Create a file with the following content, entering appropriate values where indicated, and save the file as '''values-override-init.yaml''':
 <source lang="bash"># Default values for init.
@@ Line 371: / Line 371: @@
 <source lang="bash">helm repo update
 helm search repo pulsehelmrepo/pulse</source>
-====Prepare override-pulse file (GKE and OpenShift)====
+====Prepare override-pulse file (GKE)====
 Create a file with the following content, entering appropriate values where indicated, and save the file as '''values-override-pulse.yaml''':
 <source lang="bash">
@@ Line 726: / Line 726: @@
 networkPolicies:
    enabled: false</source>
 ====Install pulse Helm chart====
 Run:
@@ Line 997: / Line 996: @@
 |structuredtext====Arbitrary UIDs===
 If your OpenShift deployment uses arbitrary UIDs, you must override the securityContext settings. By default, the user and group IDs are set to 500:500:500. If your deployment uses arbitrary UIDs, update the '''podSecurityContext''' section in the YAML file for each chart as discussed in {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}}.
-|Status=No
+|Status=Yes
 }}
 |PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97
 }}

@@ Line 9: / Line 9: @@
 |structuredtext=Before you begin the steps on this page, complete the instructions on {{Link-SomewhereInThisVersion|manual=PulsePEGuide|topic=Planning}}.
-Information you will need for shared provisioning:
+Information you require for shared provisioning:
 *Versions:
@@ Line 50: / Line 50: @@
 {{AnchorDiv|SingleNamespace}}
 ===Single namespace===
-If you plan to deploy into the Single Namespace (software-defined networking [SDN] with multi-tenant mode, where namespaces are network isolated), ensure that your environment meets the following requirements for inputs:
+Single namespace deployments have a software-defined networking (SDN) with multitenant mode, where namespaces are network isolated. If you plan to deploy Pulse into the single namespace, ensure that your environment meets the following requirements for inputs:
-*Backend services deployed into the single namespace must include the string ''pulse'':
+*Back-end services deployed into the single namespace must include the string ''pulse'':
 *:<source lang="bash"><db-host>
 <db-name>
@@ Line 66: / Line 66: @@
 |alignment=Vertical
 |structuredtext====init Helm chart===
-This chart is used to initialize the shared PostgreSQL datbase.
+This chart is used to initialize the shared PostgreSQL database.
 ====Get init Helm chart====
@@ Line 206: / Line 206: @@
 Run:
 <source lang="bash">helm upgrade --install pulse-init pulsehelmrepo/init --wait --wait-for-jobs --version=<chart-version> --namespace=pulse -f values-override-init.yaml</source>
-Command will finish with exit code 0 if installation is successful.
+If the installation is successful, the command finishes with exit code 0.
 ====Validate init Helm chart====
-Execute the following command to validate Helm chart initialization. Pulse-init job should have a Status of Completed:
+To validate Helm chart initialization, run the following command:
 <source lang="bash">kubectl get pods -n=pulse -l "app.kubernetes.io/name=init,app.kubernetes.io/instance=pulse-init"
 NAME                   READY   STATUS      RESTARTS   AGE
-pulse-init-job-5669c   0/1     Completed   0          79m</source>
+pulse-init-job-5669c   0/1     Completed   0          79m</source>If the initialization was successful, the Pulse-init job has a Status of Completed.
 ===Install pulse Helm chart===
 This chart is used for install shared part.
@@ Line 220: / Line 221: @@
 helm search repo pulsehelmrepo/pulse</source>
 ====Prepare override-pulse file====
 Create a file with the following content, entering appropriate values where indicated, and save the file as '''values-override-pulse.yaml''':
 <source lang="bash">
 # Default values for pulse.
@@ Line 403: / Line 403: @@
 Run:
 <source lang="bash">helm upgrade --install pulse pulsehelmrepo/pulse --wait --version=<chart-version>  --namespace=pulse -f values-override-pulse.yaml</source>
-Command will finish with exit code 0 if installation is successful.
+If installation is successful, the command finishes with exit code 0.
 ====Validate pulse Helm chart====
-Execute the following command to list all running Pulse pods:
+To list all running Pulse pods, run the following command:
 <source lang="bash">kubectl get pods -n=pulse -l "app.kubernetes.io/name=pulse,app.kubernetes.io/instance=pulse"
 NAME                     READY   STATUS    RESTARTS   AGE
@@ Line 418: / Line 418: @@
 ===Check logs for error===
-#Execute the following command to check the log files:
+#To check the log files, run the following command:
 #:<source lang="bash">kubectl get pods
-os logs <pulse-pod-id></source>
+os logs <pulse-pod-id></source>Where: <tt>&lt;pulse-pod-id&gt;</tt> is the pod identifier.
 ===Health validation===
-#Execute the following command to download the health validation metrics:
+#To download the health validation metrics, run the following command:
 #:'''GET /actuator/metrics/pulse.health.all'''
-#Open two console windows, and execute the following commands:
+#Open two Command Prompt windows, and run the following commands:
 ##'''Console 1''':
 ##:<source lang="bash">kubectl get pods --namespace pulse -l "app.kubernetes.io/name=pulse,app.kubernetes.io/instance=pulse" -o jsonpath="{.items[0].metadata.name}"
@@ Line 434: / Line 433: @@
 ##:<source lang="bash">curl -X GET http://127.0.0.1:8090/actuator/metrics/pulse.health.all       -H 'Content-Type: application/json'
 </source>
-#:If Pulse is running correctly and can connect to Redis and PostgreSQL, the following is returned:
+#:If Pulse is running correctly and can connect to Redis and PostgreSQL, the following results appear:
 #*http response is <tt>200</tt>
 #*json response has <tt>measurements.statistic.value</tt> of <tt>1.0</tt>, for example:
@@ Line 468: / Line 467: @@
 |structuredtext=If you encounter problems during deployment, examine the init Helm and Pulse Helm manifests.
 ===Check init Helm manifests===
-Execute the following command to output init Helm manifest files into the '''helm-template''' directory:
+To output init Helm manifest files into the '''helm-template''' directory, run the following command:
 <source lang="bash">helm template --version=<chart-version> --namespace=pulse --debug --output-dir helm-template init pulsehelmrepo/init -f values-override-init.yaml.yaml
 </source>
 Where: <tt>&lt;chart-version&gt;</tt> is the Helm chart version.
 ===Check Pulse Helm manifests===
-Execute the following command to output Pulse Helm manifest files into the '''helm-template''' directory:
+To output Pulse Helm manifest files into the '''helm-template''' directory, run the following command:
 <source lang="bash">helm template --version=<chart-version> --namespace=pulse --debug --output-dir helm-template pulse pulsehelmrepo/pulse -f values-override-pulse.yaml
 </source>
@@ Line 481: / Line 480: @@
 |sectionHeading=Override Helm chart values
 |alignment=Vertical
-|structuredtext=For more information about overriding Helm chart values, see the the "suite-level" documentation: {{SuiteLevelLink|helmoverride}}.
+|structuredtext=For more information about overriding Helm chart values, see the suite-level documentation: {{SuiteLevelLink|helmoverride}}.
 {{{!}} class="wikitable"
 {{!}}+

@@ Line 7: / Line 7: @@
 |sectionHeading=Prerequisites
 |alignment=Vertical
-|structuredtext=Please complete {{Link-SomewhereInThisVersion|manual=PulsePEGuide|topic=Planning}} instructions.
+|structuredtext=Before you begin the steps on this page, complete the instructions on {{Link-SomewhereInThisVersion|manual=PulsePEGuide|topic=Planning}}.
-Information you will need:
+Information you will need for shared provisioning:
 *Versions:
@@ Line 413: / Line 413: @@
 pulse-648b9d6666-f5d84   1/1     Running   0          22m
 pulse-648b9d6666-kqhs6   1/1     Running   0          68m</source>
 |Status=No
 }}{{Section
@@ Line 485: / Line 484: @@
 |alignment=Vertical
 |structuredtext=For more information about overriding Helm chart values, see the the "suite-level" documentation:{{SuiteLevelLink|helmoverride}}.
 {{{!}} class="wikitable"
 {{!}}+

@@ Line 305: / Line 305: @@
 Use this chart for shared Postgres database.
-'''Get init helm chart''' <source lang="text">helm repo update
+'''Get init helm chart'''
-helm search repo pe-jfrog-stage/init </source>
 '''Prepare override file'''
@@ Line 418: / Line 419: @@
 Use this chart for the shared part.
-'''Get pulse helm chart''' <source lang="text">helm repo update
+'''Get pulse helm chart'''
-helm search repo pe-jfrog-stage/pulse </source>
 '''Prepare override file'''