Configure Designer

From Genesys Documentation
Revision as of 08:13, October 4, 2021 by Marudhu.pandian@genesys.com (talk | contribs) (Published)
Jump to: navigation, search
This topic is part of the manual Designer Private Edition Guide for version Current of Designer.

Learn how to configure Designer.

Deployment configuration settings (Helm values)

The following sections provide information on the various settings that have to be configured in Designer and DAS. The configuration settings listed below will be used during the deployment of Designer and DAS. That is, these settings will be used during initial deployment/upgrade. These settings can be configured in the values.yaml Helm file.

For more information about how to override Helm chart values, see Overriding Helm chart values in the Setting up Genesys Engage Cloud Private Edition guide.
Important
Depending on the cloud platform or the container orchestration platform that you are deploying Designer on, you might have to carry out some additional steps specific to that platform. For more information, navigate to the required topic in the Cloud platform specific information section on the About page.

Designer deployment settings

The following table provides information on the Designer deployment settings. These settings are configured in the designer-values.yaml file.

Parameter Description Mandatory? Default Value
designer.deployment.replicaCount Number of service instances to be created. Mandatory 2
designer.deployment.maxreplicaCount The maximum number of replicas to be created. It is recommended to configure this setting if auto-scaling is used. Optional 10
designer.deployment.strategy The deployment strategy to follow. This determines which type of resources are deployed. Valid values are: rollingupdate, blue-green, blue-green-volume, blue-green-ingress, grafana.
  • rollingupdate - default Kubernetes update strategy where resources will be updated using the rolling upgrade strategy.
  • blue-green - for deploying and upgrading the Designer service using the blue-green strategy.
  • blue-green-volume - for the blue/green upgrade, this is to create a Persistent Volume Claim (PVC) for the very first time.
  • blue-green-ingress - for the blue/green upgrade, this is to create an ingress for the first time and update the ingress during a service cutover.
  • grafana - for deploying the Grafana dashboard.
 Mandatory rollingupdate
designer.deployment.color This is to deploy/upgrade the Designer service in a blue-green upgrade strategy. Valid values are: blue, green. Optional
designer.deployment.type This is to specify the type of deployment. Valid value: Deployment. Optional Deployment
designer.image.registry The registry that the organization uses for storing images. Mandatory
designer.image.repository Docker repository that contains the images for Designer. Mandatory
designer.image.tag Designer image version. Mandatory 9.0.110.07.7
designer.image.PullPolicy Designer image pull policy (imagePullPolicy). Valid values: Always, IfNotPresent, Never.
  • Always - always pull the image.
  • IfNotPresent - pull the image only if it does not already exist on the node.
  • Never - never pull the image.
 Mandatory IfNotPresent
designer.image.imagePullSecrets Secret name containing credentials for authenticating access to the Docker repository. Mandatory
designer.volumes.workspacePvc.create If a persistent volume is to be created, this value has to be true. Mandatory true
designer.volumes.workspacePvc.mountPath The path where the workspace volume is to be mounted inside the Designer container. Mandatory /designer/workspace

(Changing this value is not recommended.)

designer.volumes.workspacePvc.claim Persistent volume claim name for the workspace. Mandatory designer-managed-disk
designer.volumes.workspacePvc.claimSize Size of the persistent volume claim for the workspace.

The persistent volume must be equal to or greater than this size.

Mandatory
designer.volumes.workspacePvc.storageClass storageClassName provided in the persistent volume that is created for the Designer workspace (example, nfs). Mandatory
designer.volumes.logsPvc.create If a PVC volume is to be created, this value has to be true, else false. Mandatory true
designer.volumes.logsPvc.mountPath The path where the Designer logs volume is to be mounted inside the Designer container. Mandatory /designer/logs
designer.volumes.logsPvc.claim Persistent volume claim name for logs. Mandatory designer-logs
designer.volumes.logsPvc.claimSize Size of the persistent volume claim for the Designer logs.

The persistent volume must be equal to or greater than this size.

Mandatory
designer.volumes.logsPvc.storageClass storageClassName provided in the persistent volume that is created for the Designer logs  (example, nfs). Mandatory
designer.podVolumes Log and workspace persistent volume claim names and name of the volumes attached to the pod. Mandatory 
designer:
  podVolumes:
    - name: designer-pv-volume
      persistentVolumeClaim:
        claimName: designer-managed-disk
    - name: designer-log-volume
      persistentVolumeClaim:
        claimName: designer-logs
designer.volumeMounts Name and mount path of the volumes to be attached to the Designer pods. Mandatory 
volumeMounts:
    - name: designer-pv-volume
      mountPath: /designer/workspace
    - name: designer-log-volume
      mountPath: /designer/logs
designer.livenessProbe.path Designer liveness probe API path. Mandatory /health
designer.livenessProbe.containerPort Port running the container. Mandatory 8888
designer.livenessProbe.startupDelay The liveness probe will be started after a given delay as specified here. Mandatory 20
designer.livenessProbe.checkInterval The interval between each liveness probe request. Mandatory 5
designer.livenessProbe.failureCount Number of liveness probe failures after which, to mark the container as unstable or restart. Mandatory 5
designer.readinessProbe.path Designer readiness probe API path. Mandatory /health
designer.readinessProbe.containerPort Port running the container. Mandatory 8888
designer.readinessProbe.startupDelay The readiness probe will be started after a given delay as specified here. Mandatory 20
designer.readinessProbe.checkInterval The interval between each readiness probe request. Mandatory 5
designer.readinessProbe.failureCount Number of readiness probe failures after which, to mark the container as unstable or restart. Mandatory 5
designer.designerSecrets.enabled This enables providing the GWS Client ID and Secret as an input to the Designer pods. Kubernetes Secrets is used to store the GWS client credentials. Mandatory true
designer.designerSecrets.secrets GWS Client ID and GWS Client Secret. Create a new GWS Client if it does not exist. A link to information on creating a new GWS Client is provided in the Platform settings section. Mandatory
designer.service.enabled Set to true if the service must be created. Optional true
designer.service.type Service type. Valid values are: ClusterIP, NodePort, LoadBalancer. Mandatory NodePort
designer.service.port The Designer service port to be exposed in the cluster. Mandatory 8888
designer.service.targetPort The Designer application port running inside the container. Mandatory http
designer.service.nodePort Port to be exposed in case service type is NodePort. Mandatory for designer.service.type=NodePort. 30180
designer.service.termination_grace_period The period after which Kubernetes starts to delete the pods after service termination. Optional 30 seconds.
designer.ingress.enabled Set to true to enable ingress.

Ingress should be enabled for all cases except for a lab/demo setup.

Mandatory true
designer.ingress.annotations Annotations added for ingress. The Designer UI requires Session Stickiness if the replica count is more than 1. Configure Session Stickiness based on the ingress controller type. Configuration specific to ingress such as Session Stickiness can be provided here. Optional
designer.ingress.paths Ingress path Mandatory [/]
designer.ingress.hosts Hostnames to be configured in ingress for the Designer service. Mandatory - ssdev1.genhtcc.com
designer.ingress.tls TLS configuration for ingress. Optional []
designer.resources.limits.cpu Maximum amount of CPU that K8s allocates for the container. Mandatory 600m
designer.resources.limits.memory Maximum amount of memory that K8s allocates for the container. Mandatory 1Gi
designer.resources.requests.cpu Guaranteed CPU allocation for the container. Mandatory 500m
designer.resources.requests.memory Guaranteed memory allocation for the container. Mandatory 512Mi
designer.securityContext.runAsUser This setting controls which user ID the containers are run with. This can be configured to run Designer as a non-root user. You can either use the Genesys user or arbitrary UIDs. Both are supported by the Designer base image. 500 is the ID of the Genesys user.

The file system must reside within the Genesys user account in order to run Designer as a Genesys user. Change the NFS server host path to the Genesys user: chown -R genesys:genesys.

Optional
designer.securityContext.runAsGroup Controls which primary group ID the containers are run with. This can be configured to run Designer as a non-root user. You can either use the Genesys userGroup (GID - 500) or arbitrary GIDs. Both are supported by the Designer base image. Optional
designer.nodeSelector To allow pods to be scheduled based on the labels assigned to the nodes. Optional Default value:

nodeSelector: {}
Sample value:

nodeSelector:
    <label_key>: <label_value>
designer.affinity The K8s standard node affinity and anti-affinity configurations can be added here. Refer to the this topic in the Kubernetes documentation site for sample values. Optional {}
designer.tolerations Tolerations work with taints to ensure that pods are not scheduled on to inappropriate nodes. Refer to the Taints and Tolerations topic in the Kubernetes documentation site for sample values. Optional []
designer.podDisruptionBudget.enabled Set to true if a pod disruption budget is to be created. Optional false
designer.podDisruptionBudget.minAvailable The number of pods that should always be available during a disruption. Optional 1
designer.dnsPolicy The DNS policy that should be applied to the Designer pods. Optional
designer.dnsConfig The DNS configuration that should be applied to the Designer pods. Optional
designer.priorityClassName The priority class name that the pods should belong to. Optional
designer.networkPolicies.enabled Set to true if network policies are to be created. Currently, Designer does not support network policies. This setting is reserved for future use. Optional false
designer.hpa.enabled Enables K8s Horizontal Pod Autoscaler (HPA). It automatically scales the number of pods based on average CPU utilization and average memory utilization. For more information on HPA refer to this topic in the Kubernetes documentation site. Optional false
designer.hpa.targetCPUPercent The K8s HPA controller will scale up or scale down pods based on the target CPU utilization percentage specified here. It scales up or scales down pods between the range - designer.deployment.replicaCount and designer.deployment.maxreplicaCount. Optional 70
designer.hpa.targetMemoryPercent The K8s HPA controller will scale up or scale down pods based on the target memory utilization percentage specified here. It scales up or scales down pods between the range - designer.deployment.replicaCount and designer.deployment.maxreplicaCount. Optional 70
designer.labels Labels that will be added to the Designer pods. Optional {}
designer.annotations Annotations added to the Designer pods. Optional {}
designer.prometheus.enabled Set to true if Prometheus metrics must be enabled. Optional false
designer.prometheus.tagName Label key assigned to the pods/service to filter out. Optional service
designer.prometheus.tagValue Label value assigned to the pods/service to filter out. Optional designer
designer.prometheus.serviceMonitor.enabled Set to true<Set/code> if a service monitor resource is needed to monitor the pods through the Kubernetes service. Optional false
designer.prometheus.serviceMonitor.path The path in which the metrics are exposed. Optional /metrics
designer.prometheus.serviceMonitor.interval The scrape interval specified for the Prometheus server. That is, the time interval at which the Prometheus server will fetch metrics from the service. Optional 10
designer.prometheus.serviceMonitor.labels Labels to be specified for the service monitor resource. Optional
designer.prometheus.alerts.enabled Set to true<Set/code> if Prometheus alerts must to be created. Optional false
designer.prometheus.alerts.labels Labels to be specified for the alerts resource. Optional
designer.prometheus.alerts.<alert_names> Scenarios for which alerts need to be created. Optional designer.prometheus.alerts 
containerRestartAlert:
        interval: 3m
        threshold: 5
        AlertPriority: CRITICAL
      MemoryUtilization:
        interval: 1m
        threshold: 70
        AlertPriority: CRITICAL
      endpointAvailable:
        interval: 1m
        AlertPriority: CRITICAL
      CPUUtilization:
        interval: 1m
        threshold: 70
        AlertPriority: CRITICAL
      containerReadyAlert:
        interval: 1m
        readycount: 1
        AlertPriority: CRITICAL
      WorkspaceUtilization:
        interval: 3m
        threshold: 80
        workspaceClaim: designer-managed-disk
        AlertPriority: CRITICAL
      AbsentAlert:
        interval: 1m
        AlertPriority: CRITICAL
      Health:
        interval: 3m
        AlertPriority: CRITICAL
      WorkspaceHealth:
        interval: 3m
        AlertPriority: CRITICAL
      ESHealth:
        interval: 3m
        AlertPriority: CRITICAL
      GWSHealth:
        interval: 3m
        AlertPriority: CRITICAL
designer.grafana.enabled Set to true if the Grafana dashboard is to be created. Optional true
annotations Enables Kubernetes Annotations and adds it to all the resources that have been created.

For more information, refer to the Annotations topic in the Kubernetes documentation site.

Optional {}
labels Any custom labels can be configured here. It is a key and value pair, for example, key:"value". These labels are added to all resources. Optional {}
podLabels Labels that will be added to all application pods. Optional {}
podAnnotations Annotations that will be added to all application pods. Optional {}

Designer ConfigMap settings

The following table provides information on the environment variables and service-level settings stored in the Designer ConfigMap.

Parameter Description Mandatory? Default Value
designer.designerConfig.create This enables providing environment variables as an input to the Designer pods. It uses a ConfigMap to store the environment variables. Mandatory true
designer.designerConfig.envs.DES_PORT Designer port for container (port in flowsettings.json). Mandatory 8888
designer.designerConfig.envs.DES_APPSERVER_HOST DAS hostname (applicationHost in flowsettings.json). Mandatory das
designer.designerConfig.envs.DES_APPSERVER_PORT DAS port (applicationPort in flowsettings.json). Mandatory 80
designer.designerConfig.envs.DES_DEPLOY_URL This is normally not changed. It is the relative path to the workspace on DAS. The default value /workspaces should be used always (deployURL in flowsettings.json). Mandatory /workspaces
designer.designerConfig.envs.DES_USE_HTCC Set to true so Designer works with GWS. If set to false, Designer defaults to a local mode and may be used temporarily if GWS is unavailable (usehtcc in flowsettings.json). Mandatory false
designer.designerConfig.envs.DES_HTCC_SERVER GWS server host  (htccserver in flowsettings.json). For example, gws.genhtcc.com. Mandatory
designer.designerConfig.envs.DES_HTCC_PORT GWS server port (htccport in flowsettings.json). For example, 80. Mandatory 80
designer.designerConfig.envs.DES_ENABLE_ANALYTICS To enable or disable Designer Analytics (enableAnalytics in flowsettings.json). Optional false
designer.designerConfig.envs.DES_ES_URL Elasticsearch URL (esUrl in flowsettings.json). For example, http://es-service:9200. Optional
designer.designerConfig.envs.DES_ES_SERVER Elasticsearch Server Host Name (esServer in flowsettings.json). For example, es-service). Optional
designer.designerConfig.envs.DES_ES_PORT Elasticsearch port (esPort in flowsettings.json). For example, 9200. Optional 80
designer.designerConfig.envs.DES_FILE_LOGGING_ENABLED Enable file logging. If not enabled, Designer will create only verbose logs. Mandatory false

Designer-Sync settings

If the Designer workspace is stored in a cloud storage system, then DAS must use the 'StatefulSet' deployment type. In this case, Designer-Sync containers will be used to sync the designer workspace from the cloud storage system to the high-performance disks attached to the DAS pods.

Parameter Description Mandatory Default Value
designerSync.image.registry Image registry of the Designer-Sync container. Yes
designerSync.image.repository Image repository of the Designer-Sync container. Yes
designerSync.image.tag Image version of the Designer-Sync container. Yes
designerSync.resources.requests.cpu CPU resource requests needed for the Designer-Sync container. Yes
designerSync.resources.requests.memory Memory resource requests needed for the Designer-Sync container. Yes
designerSync.resources.limits.cpu CPU resource limit set for the Designer-Sync container. Yes
designerSync.resources.limits.memory Memory resource limit set for the Designer-Sync container. Yes
designerSync.livenessProbe.healthScript The path of the script that needs to be executed to check the health of the container. Yes /workspace_sync/health.sh
designerSync.livenessProbe.timeoutSeconds Timeout for the liveness probe check. Yes 5
designerSync.livenessProbe.checkInterval Interval at which successive liveness probe checks are executed. Yes 10
designerSync.livenessProbe.failureCount Number of failures after which it is decided that the container's health is unstable. Yes 3
designerSync.volumeMounts Volumes and mounts configuration for the Designer-Sync container image. Yes

Designer-Sync ConfigMap settings

Parameter Description Mandatory Default Value
designerSync.designerSyncConfig.create To specify if a ConfigMap must be created for the Designer-Sync container. Yes true
designerSync.designerSyncConfig.envs.MODE To set the mode for Designer-Sync. There are 2 modes:
  • initial - imports the Designer workspace from the cloud storage system to the disks attached to the DAS pods.
  • periodic - periodically syncs incoming changes in the Designer workspace to disks attached to the DAS pods.
 Yes periodic
designerSync.designerSyncConfig.envs.LOCATION Location name. For example, westus2. No
designerSync.designerSyncConfig.envs.RSYNC_INTERVAL The periodic RSYNC execution interval. No 60
designerSync.designerSyncConfig.envs.WORKSPACE_RSYNC_MOUNT_0 Persistent volume mount name from which the data must be synced. Yes
designerSync.initialDesignerSyncConfig.create Set to true to create a ConfigMap for the Designer-Sync container during the initial import. Yes true
designerSync.initialDesignerSyncConfig.envs.MODE Initial mode of Designer-Sync. Yes initial
designerSync.initialDesignerSyncConfig.envs.LOCATION Location of the cloud deployment. No
designerSync.initialDesignerSyncConfig.envs.WORKSPACE_RSYNC_MOUNT_0 Persistent volume mount name from which the data must be imported. Yes

DAS deployment settings

The following table provides information on the DAS deployment settings. These settings are configured in the das-values.yaml file. DAS Deployment Settings

Parameter Description Mandatory? Default Value
das.deployment.replicaCount Number of pods to be created. Mandatory 2
das.deployment.maxreplicaCount The maximum number of replicas to be created. It is recommended to configure this setting if auto-scaling is used. Optional 10
das.deployment.strategy The deployment strategy to follow. This determines which type of resources are deployed. Valid values are: rollingupdate, blue-green, blue-green-ingress, blue-green-service, canary.
  • rollingupdate - default Kubernetes update strategy where resources will be updated using the rolling upgrade strategy.
  • blue-green - for deploying and upgrading the DAS service using the blue-green strategy.
  • blue-green-ingress - for the blue-green upgrade, this is to create an ingress for the first time.
  • blue-green-service - for the blue-green upgrade, this is to create a service for the first time, and update the service during a service cutover.
  • canary - to deploy canary pods along with the blue-green pods.
 Mandatory rollingupdate
das.deployment.color This is to deploy/upgrade the DAS service using the blue-green upgrade strategy. Valid values are: blue, green. Mandatory for blue-green and blue-green-service strategies.
das.deployment.type Type of Kubernetes controller. Valid values is: StatefulSet
  • StatefulSet - if the Designer workspace is stored in a remote cloud storage system, such as Azure Files.
 Optional StatefulSet
das.image.registry The registry that the organization uses for storing images. Mandatory
das.image.repository Docker repository for DAS. Mandatory
das.image.tag DAS image version. Mandatory 9.0.106.03.7
das.image.pullPolicy DAS image pull policy (imagePullPolicy). Valid values are: Always, IfNotPresent, Never.
  • Always - always pull the image.
  • IfNotPresent - pull the image only if it does not already exist on the node.
  • Never - never pull the image.
 Optional IfNotPresent
das.image.imagePullSecrets Secret name containing the credentials for authenticating access to the Docker repository. Mandatory
das.podVolumes Provides the name of the volume and name of the persistent volume claim to be attached to the pods Mandatory 
das:
podVolumes:
- name: workspace
 persistentVolumeClaim:
 claimName: designer-managed-disk
 - name: logs
 persistentVolumeClaim:
 claimName: designer-logs
das.volumes.podPvc.create If a persistent volume is to be created, this value has to be true. Optional false
das.volumes.podPvc.mountPath The path where the workspace volume is to be mounted inside the DAS container. Optional
das.volumes.podPvc.claim Persistent volume claim name for the volume. Optional
das.volumes.podPvc.claimSize Size of the persistent volume claim for the pod.

The persistent volume must be equal to or greater than this size.

Optional
das.volumes.podPvc.storageClass storageClassName provided in the persistent volume that is created for DAS (example, nfs). Optional
das.volumes.podPvc.accessModes The read/write priveleges and mount priveleges of the volume claim with respect to the nodes. Valid types are: ReadWriteOnce, ReadOnlyMany, ReadWriteMany.
  • ReadWriteOnce - the volume can be mounted as read-write by a single node.
  • ReadOnlyMany - the volume can be mounted as read-only by many nodes.
  • ReadWriteMany - the volume can be mounted as read-write by many nodes.

For more information, refer to the access modes topic in the Kubernetes documentation site.

Optional ReadWriteOnce
das.volumeMounts The name of the volume and the mount path to be used by the pods. Mandatory 
volumeMounts:
- mountPath: /das/www/workspaces
name: workspace
- mountPath: /das/log
name: logs
das.dasSecrets.enabled Set to true if Kubernetes secrets must be created to store keys/credentials/tokens. Optional false
das.dasSecrets.secrets Key and value pairs containing the secrets, such as a username and password. Optional
das.livenessProbe.path DAS liveness probe API path. Mandatory /health
das.livenessProbe.containerPort Port running the container. Mandatory 8081
das.livenessProbe.startupDelay The liveness probe will be started after a given delay as specified here. Mandatory 10
das.livenessProbe.checkInterval The interval between each liveness probe request. Mandatory 5
das.livenessProbe.failureCount Number of liveness probe failures after which, to mark the container as unstable or restart. Mandatory 3
das.readinessProbe.path DAS readiness probe API path. Mandatory /health
das.readinessProbe.containerPort Port running the container. Mandatory 8081
das.readinessProbe.startupDelay The readiness probe will be started after a given delay as specified here. Mandatory 10
das.readinessProbe.checkInterval The interval between each readiness probe request. Mandatory 5
das.readinessProbe.failureCount Number of readiness probe failures after which, to mark the container as unstable or restart. Mandatory 3
das.service.enabled Set to true if the service must be created. Optional true
das.service.type Service type. Valid values are: ClusterIP, NodePort, LoadBalancer. Mandatory NodePort
das.service.port The DAS service port to be exposed in the cluster. Mandatory 80
das.service.targetPort The DAS application port running inside the container. Mandatory http
das.service.nodePort Port to be exposed in case service type is NodePort. Mandatory if das.service.type is NodePort. 30280
das.service.termination_grace_period The period after which Kubernetes starts to delete the pods in case of deletion. Optional 30 seconds.
das.ingress.enabled Set to true to enable ingress.

Ingress should be enabled for all cases except for a lab/demo setup.

Mandatory true
das.ingress.annotations Annotations added for the ingress resources. Optional
das.ingress.paths Ingress path. Mandatory [/]
das.ingress.hosts Hostnames to be configured in ingress for the DAS service. Mandatory
das.ingress.tls TLS configuration for ingress. Optional []
das.resources.limits.cpu Maximum amount of CPU that K8s allocates for the container. Mandatory

600m

das.resources.limits.memory Maximum amount of memory that K8s allocates for the container. Mandatory

1Gi

das.resources.requests.cpu Guaranteed CPU allocation for the container. Mandatory 400m
das.resources.requests.memory Guaranteed memory allocation for the container. Mandatory 512Mi
das.securityContext.runAsUser This setting controls which user ID the containers are run with and can be configured to run DAS as a non-root user. You can either use the Genesys user or arbitrary UIDs. Both are supported by the DAS base image. 500 is the ID of the Genesys user.

For more information refer to the Security Context topic in the Kubernetes documentation site.

Optional
das.securityContext.runAsGroup This setting controls which primary group ID the containers are run with and can be configured to run DAS as a non-root user. You can either use the Genesys userGroup (GID - 500) or arbitrary GIDs. Both are supported by the DAS base image. Optional
das.nodeSelector To allow pods to be scheduled based on the labels assigned to the nodes. Optional Default value:

nodeSelector: {} Sample value: 

nodeSelector:
    <label_key>: <label_value>
das.affinity The K8s standard node affinity and anti-affinity configurations can be added here. Refer to the this topic in the Kubernetes documentation site for sample values. Optional {}
das.tolerations Tolerations work with taints to ensure that pods are not scheduled on to inappropriate nodes. Refer to the Taints and Tolerations topic in the Kubernetes documentation site for sample values. Optional []
das.podDisruptionBudget.enabled Set to true if a pod disruption budget is to be created. Optional false
das.podDisruptionBudget.minAvailable The number of pods that should always be available during a disruption. Optional 1
das.dnsPolicy The DNS policy that should be applied to the DAS pods. Optional
das.dnsConfig The DNS configuration that should be applied to the DAS pods. Optional
das.priorityClassName The priority class name that the pods should belong to. Optional
das.networkPolicies.enabled Set to true if network policies are to be created. Currently, DAS does not support network policies. This setting is reserved for future use. Optional false
das.hpa.enabled Set to true if the K8s Horizontal Pod Autoscaler (HPA) must be enabled. Optional false
das.hpa.targetCPUPercent The K8s HPA controller will scale up/down pods based on the target CPU utilization percentage specified. It scale up/down pods between the range deployment.replicaCount to deployment.maxReplicas Optional 75
das.hpa.targetMemoryPercent The K8s HPA controller will scale up or scale down pods based on the target CPU utilization percentage specified here. It scales up or scales down pods between the range - deployment.replicaCount and deployment.maxReplicas. Optional 70
das.labels Labels that will be added to the DAS pods. Optional {}
das.annotations Annotations added to the DAS pods. Optional {}
das.prometheus.enabled Set to true if Prometheus metrics must be enabled. Optional false
das.prometheus.tagName Label key assigned to the pods/service to filter out. Optional service
das.prometheus.tagValue Label key assigned to the pods/service to filter out. Optional designer
das.prometheus.serviceMonitor.enabled Set to true<Set/code> if a service monitor resource is needed to monitor the pods through the Kubernetes service. Optional false
das.prometheus.serviceMonitor.path The path in which the metrics are exposed. Optional /metrics
das.prometheus.serviceMonitor.interval The scrape interval specified for the Prometheus server. That is, the time interval at which the Prometheus server will fetch metrics from the service. Optional 10
das.prometheus.serviceMonitor.labels Labels to be specified for the service monitor resource. Optional
das.prometheus.alerts.enabled Set to true<Set/code> if Prometheus alerts must to be created. Optional false
das.prometheus.alerts.labels Labels to be specified for the alerts resource. Optional
das.prometheus.alerts.<alert_names> Scenarios for which alerts need to be created. Optional 
containerRestartAlert:
interval: 3m
threshold: 5
AlertPriority: CRITICAL
MemoryUtilization:
interval: 1m
threshold: 75
AlertPriority: CRITICAL
endpointAvailable:
interval: 1m
AlertPriority: CRITICAL
CPUUtilization:
interval: 1m
threshold: 75
AlertPriority: CRITICAL
containerReadyAlert:
interval: 5m
readycount: 1
AlertPriority: CRITICAL
rsyncContainerReadyAlert:
interval: 5m
readycount: 1
AlertPriority: CRITICAL
WorkspaceUtilization:
interval: 3m
threshold: 70
workspaceClaim: designer-managed-disk
AlertPriority: CRITICAL
AbsentAlert:
interval: 1m
AlertPriority: CRITICAL
LocalWorkspaceUtilization:
interval: 3m
threshold: 70
AlertPriority: CRITICAL
Health:
interval: 3m
AlertPriority: CRITICAL
WorkspaceHealth:
interval: 3m
AlertPriority: CRITICAL
PHPHealth:
interval: 3m
AlertPriority: CRITICAL
ProxyHealth:
interval: 3m
AlertPriority: CRITICAL
das.grafana.enabled Set to true if the Grafana dashboard is to be created. Optional true
annotations Enables Kubernetes Annotations and adds it to all the resources that have been created.

For more information, refer to the Annotations topic in the Kubernetes documentation site.

Optional {}
labels Any custom labels can be configured here. It is a key and value pair, for example, key:"value". These labels are added to all resources. Optional {}
podLabels Labels that will be added to all application pods. Optional {}
podAnnotations Annotations that will be added to all application pods. Optional {}

DAS ConfigMap settings

Parameter Description Mandatory? Default Value
das.dasConfig.create This setting enables providing environment variables as an input to the DAS pods. It uses a ConfigMap to store the environment variables. Mandatory true
das.dasConfig.envs.DAS_FILE_LOGGING_ENABLED Enables file logging. DAS supports only std out logging. This should always be set to false. Mandatory false
das.dasConfig.envs.DAS_LOG_LEVEL Enables log levels. Valid values are: FATAL, ERROR, WARN, INFO, DEBUG, TRACE. Optional DEBUG
das.dasConfig.envs.DAS_STDOUT_LOGGING_ENABLE Enables standard output console logging. Mandatory true
das.dasConfig.envs.DAS_SERVICES_ELASTICSEARCH_ENABLED To enable Designer Analytics. This configuration is required for DAS to initialize ES templates. Optional false
das.dasConfig.envs.DAS_SERVICES_ELASTICSEARCH_HOST Elasticsearch server host name with http:// prefix. For example, http://es-service. Optional
das.dasConfig.envs.DAS_SERVICES_ELASTICSEARCH_PORT Elasticsearch port. For example, 80. Optional 9200

Post deployment Designer configuration settings

Post deployment, Designer configuration is managed from the following 3 locations:

Flow settings

Flow Settings is used for controlling global Designer settings that are applicable to all tenants and it contains bootstrap configuration settings such as port, GWS info, and DAS URL.

Configuration path - /workspace/designer/flowsettings.json.

This will be configured using the helm install. Refer to the Update the flowsettings.json file section for information on updating the flowsettings.json file.

Tenant settings

These are tenant specific settings if the Designer service is configured with multi-tenancy .

Configuration  path - workspace/<contactcenter-Id>/config/tenantsettings.json.

The user should logout and log back in after any changes to the tenantsettings.json file. The Designer UI will continue to show the older features until the user logs out and logs back in.

Tenant specific settings are configured by directly editing the file in the above path.

DesignerEnv transaction list

The DesignerEnv transaction list is available in Configuration Server (Tenant/Transactions/DesignerEnv). This is mostly used to control the run-time settings. Any change to the DesignerEnv transaction list does not require the application to be published again or a new build for the application.

The user should log out and log back in for the changes to reflect in the Designer UI.

The DesignerEnv transaction list is configured using Agent Setup.

Post deployment configuration settings reference table

Category: Analytics
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
enableAnalytics
(optional) 		Yes Yes No This flag enables or disables the analytics feature.

Sample value: true
Default value: false

esUrl
(optional) 		Yes Yes No Elasticsearch URL

Sample value: http://es-spot.usw1.genhtcc.com:80

esServer
(optional) 		Yes Yes No Elasticsearch server host name (for example, es-service). Sample value: es-spot.usw1.genhtcc.com
esPort
(optional) 		Yes Yes No Elasticsearch port. Sample value: 80
ReportingURL
(optional) 		No No Yes

Section: reporting

URL of Elasticsearch where Designer applications will report data.

Sample value: http://es-spot.usw1.genhtcc.com:80

esMaxQueryDuration
(optional) 		Yes Yes No The maximum time range (in days) to query in Designer Analytics. Each day's data is stored in a separate index in Elasticsearch.

Sample value: 90
Default value: 90

sdrMaxObjCount
(optional) 		Yes Yes No The maximum count of nested type objects that will be captured in SDRs. When set to -1, which is the default value, no objects will be trimmed. All the milestones or activities visited in runtime are expected to be captured in an SDR.

Sample value: 20

SdrTraceLevel
(optional) 		Yes Yes No Value are:
  • 100 — Debug level and up. Currently, there are no Debug messages.
  • 200 — Standard level and up. This setting will show all blocks that are entered during a call in the blocks array.
  • 300 — Important level and up. This setting filters out all blocks from the blocks array, except those containing data that will change from call to call (such as the Menu block and User Input block).

Sample value: 300
Default value: 300

Category: Audit
Setting Name lowsettings.json tenantsettings.json DesignerEnv Description Value
enableESAuditLogs
(optional) 		Yes Yes No Enable or disable audit logs captured in Elasticsearch.

Sample value: false
Default value: false

enableFSAuditLogs
(optional) 		Yes Yes No Enable or Disable audit logs captured in the file system under the logs directory or in standard output.

Sample value: true
Default value: true

maxAppSizeCompare
(optional) 		Yes Yes No The maximum size of data object for which a difference will be captured in the audit logs, value in bytes. That is, the difference between the Designer object's old value and new value.

Sample value: 1000000
Default value: 1000000

enableReadAuditLogs
(optional) 		Yes Yes No Control whether reading of Designer objects is captured in audit trails. If enabled any Designer object viewed in the UI will be recorded in the audit logs.

Sample value: false
Default value: false

Category: Authorization
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
disableRBAC
(optional) 		Yes Yes No Controls if Designer reads and enforces permissions associated with the logged in user's roles.

Sample value: false
Default value: false

rbacSection
(optional) 		Yes Yes No In a Role object, the name of the section within the Annex where the privileges are stored.

Sample value: CfgGenesysAdministratorServer
Default value: CfgGenesysAdministratorServer

disablePBAC
(optional) 		Yes Yes No Controls if Designer allows partitioning of the Designer workspace and restricts a user's access to Designer objects in the user's partitions.

Sample value: false
Default value: false

Category: Collaboration
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
locking
(optional) 		Yes No No The type of locking used, in an editing session for applications, modules, or data tables. Valid values are: file, redis, none.
  • none - resources are not locked and can be edited simultaneously by multiple users which can result in one user overwriting another user's changes.
  • file - uses files to keep track of locks and relies on shared storage (for example, NFS) to make lock files available to each Designer pod. Lock files are stored in the same location as the user's Designer workspace.
  • redis - uses Redis for storing resource locks and is recommended for production environments.

Sample value: file
Default value: file

Category: DAS
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
applicationHost
(mandatory) 		Yes No No The server name Designer uses to generate the URL to the application. ORS and MCP fetch the application code and other resources from this URL.

Sample value: das.usw1.genhtcc.com
Default value: localhost

applicationPort Yes No No The corresponding port to be used with applicationHost.

Sample value: 80
Default value: 80

deployURL Yes No No This is normally not changed. It is the relative path to the workspace on DAS.

Sample value: /workspace
Default value: /workspace

Category: Digital
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
rootsSRL
(optional) 		Yes Yes No If specified, this is used to filter which Root Categories to display when selecting Standard Responses.

Sample value: Any REGular EXpression (REGEX).

maxFlowEntryCount
(optional) 		Yes No Yes

Section: flowsettings

Specify how many times the same application can process a specific digital interaction.

Sample value: 20
Default value: 20

Category: External APIs
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
httpProxy
(optional) 		Yes Yes Yes

Secion: flowsettings

Specify the proxy used for external requests and nexus API calls (if enable_proxy is true).

Sample value: [http://vpcproxy-000-int.geo.genprim.com:8080

redundantHttpProxy
(optional) 		Yes Yes Yes

Section: flowsettings

Specify the backup proxy used for external requests and nexus API calls (if enable_proxy is true), when httpProxy is down.

Sample value: [http://vpcproxy-001-int.geo.genprim.com:8080

Category: Features
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
features Yes Yes No This is an object. See the 5.5 Features section for a list of supported features.

Default value: 

{
  nexus: true,
  enableBulkAudioImport: true
}
Category: GWS
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
usehtcc Yes No No Set to true so that Designer works with GWS. If set to false, Designer defaults to a local mode and may be used temporarily if GWS is unavailable.

Sample value: true
Default value: false

htccServer Yes No No GWS Server

Sample value: gws-usw1-int.genhtcc.com
Default value: gws-usw1-int.genhtcc.com

htccport Yes No No GWS port.

Sample value: 80
Default value: 80

ssoLoginUrl Yes No No URL of GWS authentication UI. Designer redirects to this URL for authentication.

Sample value: https://gws-usw1.genhtcc.com
Default value: https://gws-usw1.genhtcc.com

maxConcurrentHTCCRequest
(optional) 		Yes No No For batch operations to GWS, the max number of concurrent requests that Designer will send to GWS.

Sample value: 5
Default value: 5

batchOperationResultTTL
(optional) 		Yes No No For batch operations to GWS, the time, in milliseconds, for which duration Designer stores the results of a batch operation on the server, before deleting them.

Sample value: 100000
Default value: 100000

Category: Help
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
docsMicroserviceURL
(optional) 		Yes No No URL for Designer documentation.

Default value: https://docs.genesys.com/Documentation/PSAAS/Public/Administrator/Designer

Category: IVR
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
recordingType
(optional) 		Yes Yes No Specify the recording type to be used in Record block. Set as GIR. If the option is missing or blank, Full Call Recording type will be used.

Sample value: GIR
Default value: GIR

Category: Logging
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value 
logging: {
designer: { level:
debug },
audit: { level: trace},
auditdebug: { level: debug },
cli: { level: debug }
}

(optional)

Yes No No Specify Designer log levels. Each field has valid values: trace, debug, info, warn, error, or fatal.
  • designer - log level of Designer.
  • audit - log level of audit.
  • auditdebug - log level of audit debug, this will log detailed audit information.
  • cli - log level for cli commands executed on Designer.

Sample value:

logging: {
designer: { level: debug},
audit: { level: trace },
auditdebug: { level: debug},
cli: { level: debug }
}

Default value:
logging: {
designer: { level: debug },
audit: { level: trace },
auditdebug: { level: debug },
cli: { level: debug }
}
Category: Nexus
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
url
(optional) 		No No Yes

Section: nexus

URL of Nexus that typically includes the API version path. For example, https://nexus-server/nexus/api/v3.

Default value: http://nex-dev.usw1.genhtcc.com

password
(optional) 		No No Yes

Section: nexus

The Nexus x-api-key created by Nexus deployment.

Default value: dc4qeiro13nsof569dfn234smf

enable_proxy
(optional) 		No No Yes

Section: nexus

Boolean value to indicate if httpProxy is used to reach Nexus.

Default value: false

profile
(optional) 		No No Yes

Section: nexus

Enable Contact Identification via Nexus (for example, to enable Last Called Agent routing).
Category: Process
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
port Yes No No Designer process port in the container. Normally, the default value should be left as is.

Sample value: 8888
Defualt value: 3000

Category: Provisioning
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
primarySwitch
(optional) 		Yes Yes No Specify the primary switch name if more than one switch is defined for the tenant. Designer fetches and works with route points from this switch.

Default value: us-west-1

Category: Routing
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
ewtRefreshTimeout
(optional) 		NO No Yes

Section: flowsettings

Specify the interval (in seconds) at which to refresh the Estimated Waiting Time when routing an interaction.

Sample value: 5
Default value: 1

Category: Redis
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value 
redis: {
host: "",
port: "",
tlsEnabled: true,
lockTimeout: 120,
listTimeout: 1800
}

(optional) 		Yes No No Used by Designer for resource index caching and multi-user collaboration locks on Designer resources.

It is a separate object that contains:

  • host - Redis host name.
  • port - Redis port.
  • tlsEnabled - TLS enabled or not.
  • lockTimeout - Timeout, in seconds, before a resource lock is released for an editing session of applications, modules, or data tables.
  • listTimeout - The cache expiry timeout (in seconds) of the application list and shared modules list. By default, it is 30 minutes. That is, any new application/modules created in the UI will be seen in the listing page after 30 mins. It can be reduced to a smaller value. This is to improve the page loading performance of the Applications and Shared Modules page. A better performance is achieved with a higher value.

Sample value:

redis: {
host: "",
port: "",
tlsEnabled: true,
lockTimeout: 120,
listTimeout: 1800
}

Default value:
redis: {
host: redis.server.genhtcc.com,
port: 6379,
tlsEnabled: true,
lockTimeout: 120,
listTimeout: 1800
}
Category: Security
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
zipFileSizeLimitInMegaBytes
(optional) 		Yes Yes No Defines the maximum zipFile size limit (in megabytes) during bulk audio import.

Sample value: 50

disableCSRF
(optional) 		Yes Yes No Disable CSRF attack protection. For more information, refer to this topic in the CWE site.

By default, CSRF attack protection is enabled. It can be disabled by setting this flag to true.

Sample value: false
Default value: false

disableSecureCookie
(optional) 		Yes No No Disables the secure cookies header.

Sample value: false
Default value: false

Category: Session
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
idleTimeout
(optional) 		Yes Yes No Idle timeout, in seconds, before a user session is terminated while editing applications, modules, or data tables.

Sample value: 840
Default value: 840

lockTimeout
(optional) 		Yes Yes No Timeout, in seconds, before a resource lock is released, for an editing session of applications, modules, or data tables.

Sample value: 120
Default value: 120

lockKeepalive
(optional) 		Yes Yes No Interval, in seconds, before the client sends a ping to the server, to refresh the lock for an editing session of applications, modules, or data tables.

Sample value: 15
Default value: 15

Category: Workflow
Setting Name flowsettings.json tenantsettings.json DesignerEnv Description Value
maxBuilds
(optional) 		Yes Yes No Specify the maximum number of builds allowed per application.

Sample value: 20
Default value: 20

enablePTE
(optional) 		No No Yes

Section: flowsettings

Boolean value to indicate if PTE objects are enabled at runtime.

Sample value: true
Default value: false

Features

The features specified in this section are configured under the features object in the flowsettings.json file or the tenantsettings.json file.

For example, 

"features": {
           "nexus": true,
..
}
Important
These features are configured only in the flowsettings.json file and the tenantsettings.json file, and not in the DesignerEnv transaction list.
Category Feature Setting Name Mandatory flowsettings.json tenantsettings.json Description Default Value
Audio enableBulkAudioImport Optional Yes Yes Enable/disable the bulk audio import feature. false
grammarValidation Optional Yes yes If this feature is enabled, Designer will validate invalid grammar files during grammar upload and you can upload only valid grammar files (GRXML or Nuance compiled binary grammar files). false
Nexus nexus Optional Yes Yes Enable/disable the Nexus feature. false
Survey survey Optional Yes Yes Enable/disable the survey feature. true
UI Plugins plugins Optional Yes Yes Plugin configuration details.

(Steps are given below the table.)

{}
plugins Optional Yes Yes Enable or disable the plugin feature. false
Milestone enableImplicitModuleMilestones Optional Yes Yes Enable reporting each Shared Module call as an internal milestone. If disabled, Shared Module calls will not generate a milestone. false

Adding a UI plugin to Designer

  1. Add the plugins array object in the flowsettings.json file (/ofs/designer/flowsettings.json).
    The plugins object contains all the input properties for the plugin app. This is a required property. Whenever there is a change in this object, refresh the browser for the changes to take effect.
    Example:
    "plugins": [
    {
      "url": "http://genesysexample.com/",
      "displayName": "Nexus PII Management",
      "placement": "messageCollections",
      "id":   "nexuspii",
      "mappings": {
            "prod": {
                "G1-AUS4": "https://genesysexample.com/admin/ux"
            },
            "staging": {
                "G1-USW1": "http://genesysexample.com/"
            },
        }
    },
    {
       ...
    }]
  2. Add the csplist array object in the flowsettings.json file (/ofs/designer/flowsettings.json).
    The cspList object contains the URL forms to be allowed by Designer's security policy. This is a required property. Whenever there is a change in this object, re-start the node container for the changes to take effect.
    Example:
    If the URL is http://genesysexample.com/, the cspList would be:
    "cspList": ["*.genexample1.com:*", "*.genexample2.com:*", "*.genexample3.com:*"]
  3. Turn on the plugins and nexus feature flags in the Designer tenantSettings.json file (/ofs/<tenantId>/config/tenantSettings.json).
    This is a required property. Whenever there is a change in this object, log out of Designer and log in again for the changes to take effect.
    Important
    If you want to enable the plugins feature for all tenants, add this feature flag in the flowsettings.json file. The feature is enabled for all the tenants under that bucket.
    Example:
    {
    "features": {
        "plugins": true,
        "nexus": true
}}
  4. Add the url_<plugin-id> property in Agent Setup. This section is for the tenant URL override. If the DesignerEnv setting (Transactions/Internal/DesignerEnv) is not provided the plugin URL from the flowsettings.json file is considered.
    This is an optional property. Whenever there is a change in this object, log out of Designer and log in again for the changes to take effect.
    Example:
    {"url_<plugin-id>" : "https://plugin-genesysexample.com"}
Retrieved from "https://all.docs.genesys.com/DES/Current/DESPEGuide/Configure (2025-07-18 13:00:18)"
Comments or questions about this documentation? Contact us for support!