-
Go to place regarding gap docs - https://gap-docs.gservice.emarsys.net/
-
-
(optional) script to setup gcloud and kubectl setup-cluster.sh
-
sets up kubectl context with default namespace
-
run GAP_ACCOUNT=first.last@emarsys.com GAP_PROJECT=ems-gap-production GAP_NAMESPACE=mobile-engage ./cluster-setup.sh # for production
-
use kubectl config use-context gap-production # to switch context
-
-
-
Kubernetes concepts
-
k8s cluster gap-stage gap-production
-
Cloud Build History
-
k8s workloads
-
Pod metrics
-
Environment variables
-
managed with cli interface gap-cli
-
or with UI interface gap-secret-editor
-
e.g: gap-cli config:edit -a me-inbox
-
-
lives in kubernetes secrets
-
kubectl get secret -n mobile-engage
-
-
change is immediate and causes a restart (triggered by gap-cli)
-
-
logging to laas in index 'gap-*'
-
Redis (Cloud Memorystore) and Postgres (Cloud SQL) instances They are located in the same project of the application, e.g. ems-gap-me-inbox-s for staging and ems-gap-me-inbox-p for production. Some of them (like inbox) are behind a VPC perimeter, so you need to be in the VPN to access them and you need to use proxy in the browser to view them. FoxyProxy for Firefox type browsers, Proxy Switcher And Manager for Chrome type browsers.