Designer on AKS

This topic is part of the manual Designer Private Edition Guide for version Current of Designer.

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-server=pureengage-docker-staging.jfrog.io \
--docker-username=<camelot-username> \
--docker-password=<API key from jfrog> \
--docker-email=<emailid>

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:

htccserver: gws-service-proxy.gws.svc.cluster.local
gwsenvurl: http://gauth-environment.gauth.svc.cluster.local:80
gwsauthurl: http://gauth-auth.gauth.svc.cluster.local:8
ssoLoginUrl: https://gauth.apps.<DOMAIN>

Checking logs

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

Designer

kubectl get pods

kubectl logs <designer-pods-id>

DAS