Designer on GKE

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Designer Private Edition Guide for version Current of Designer.

Learn more about specific settings that you have to configure when deploying Designer on Google Kubernetes Engine (GKE).

Configure and deploy Designer as described in the topics under the Configure and deploy section. Only additional information that is specific to deploying Designer on GKE is provided here.

Configure a secret to access JFrog

If you haven't done so already, create a secret for accessing the JFrog registry (for example, jfrog-stage-credentials):

kubectl create secret docker-registry jfrog-stage-credentials \ \
--docker-username=<camelot-username> \
--docker-password=<API key from jfrog> \

Now map the secret to the default service account:

kubectl secrets link default jfrog-stage-credentials --for=pull

Create a Designer secret with GWS

To create a Designer secret with GWS, update the following values to your Environment in the GWS service:

  • <internal-api-url-gws>: Set to the internal API of GWS
  • contactCenterIds: Set to your tenant ID
  • redirectURIs: Set to the URL(s) to be used for Designer
  • <DOMAIN>: Set to the domain address for the environment

And, optionally, update the following:

  • -u opsAdmin: opsPass (this is the default delivered for tenants)
  • client_secret: Set to any value (used in secret)
  • name: Set to anything
  • client_id: Set to your client ID (used in secret)

GWS settings for auth

In the Designer flowsettings override file, update the following options with these values:

Checking logs

After deploying Designer, you check the logs using the following commands:


kubectl get pods

kubectl logs <designer-pods-id>


kubectl get pods

kubectl logs <das-pods-id>

Retrieved from " (2024-04-15 20:20:34)"
Comments or questions about this documentation? Contact us for support!