GCP GKE Mendix Private Cloud Quickstart

Scripted install of GKE Cluster in Google Cloud.
Install Nginx Ingress controllers
Configure Namespace for Mendix either for Connected or Standalone mode
Deploys a demo Mendix application
If Standalone mode is selected, it also installs Tekton Pipelines and Dashboard
Installs Grafana, Prometheus and Loki.

- Install the gcloud CLI : https://cloud.google.com/sdk/docs/install
- Initialize the gcloud CLI: https://cloud.google.com/sdk/docs/initializing
- A valid GCP subscription
- kubectl
- helm

• export PROJECT_ID= TODO

• export GKE_ARTIFACTS_REGISTRY=mendix-test

• export GKE_CLUSTER_NAME=mendix-quickstart

• export GKE_REGION=TODO ` #Connected Mode

• export CLUSTER_ID=TODO

• export CLUSTER_SECRET=TODO

• export AKS_NAMESPACE= TODO`

#Tekton

• export PATH_TO_HELM= TODO # usually the current working directory
• export URL_TO_YOUR_REPO_WITHOUT_TAG=TODO
• export YOUR_NAMESPACE=TODO # where Mendix Operator is installed
• export SOME_UNIQUE_NAME=TODO

Your Mac's security settings may prevent the downloaded mxpc-cli from executing.

. ./mxpc-cli -help

Default is connected mode

. ./do-all.sh connected
      or
. ./do-all.sh standalone

Mendix application will be available at appurl seen in MendixCR or at Ingress ( kubectl get ing -A)

Available at the external ip address of the prometheus svc port 9090

kubectl get svc -n grafana | grep -i Loadbalancer

Example: http://ab5b2c0d274690ae9d506d21ed876-1145176934.us-east-2.elb.amazonaws.com:9090/

• Tekton dashboard will be exposed at port 9097
• Tekton listener will be forwarded to port 8080 ( only Generic HTTP listener is installed in the procedure).`

./del-gke-cluster.sh will delete the cluster and artifacts

Install the Mendix components on the cluster using the instructions here - https://docs.mendix.com/developerportal/deploy/private-cloud-cli-non-interactive