Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Access the Google Kubernetes Engine console. In the Clusters page, click on the Create cluster button.

Image Modified

You will be presented with several configuration pages. Adjust the cluster configuration as desired, or just use the default values.

...

Warning
Do take note of the Zone used as this will be used for storage configuration later.

Image Modified

In the Node Pools page, you can configure the number of nodes and scaling options.

Image Modified

Under the Nodes page, you can choose the machine configuration to specify the machine type, CPU and disk options.

Image Modified

Click on the CREATE button at the bottom to start creating the cluster.

When the cluster has been created, you will see a tick next to the cluster name, and a Connect button will become available.

Image Modified


2. Deploy MariaDB Database

...

In the Marketplace, search for MariaDB, click on the MariaDB entry and click on the Configure button.

Image Modified

Image Modified

Change the configuration as required, or just use the default values, and click on Deploy. Wait for a few minutes while the MariaDB instance is starting.

Image Modified

Image Modified

Once the status is OK, click on the name and view the details. Under Details, look for MariaDB root password and click on preview secret data

Warning
Copy the database root password and service name for the database setup later.

Image Modified


3. Deploy Google Cloud Filestore Persistent Volume

...

Access the Google Cloud Filestore console. The first time you access it, you will need to click on the Enable button.

Image Modified

In the Instances page, click on the Create Instance button.

Image Modified

Key in an Instance IDFile share name and Region/Zone, then click on the Create button.

...

Warning
IMPORTANT: You must create the Filestore instance in the same zone as your Kubernetes cluster for it to be accessible to the cluster.

Image Modified

Once the instance has been initialized, take note of the IP address and File share name to be used later.

Image Modified


4. Deploy Joget DX

...

In the GKE Clusters page, click on the Connect button for your cluster, then Run in Cloud Shell.

Image Modified

Image Modified

Once you have access to the Cloud Shell command line, use your favourite editor (e.g. vi or nano) to save your YAML into a file.

...

Code Block
languagebash
kubectl apply -f joget-dx7-tomcat9-gke.yaml


Image Modified

Wait for a few minutes while the required Kubernetes objects (Deployment, PersistentVolume, PersistentVolumeClaim, Deployment, Service and ClusterRoleBinding) are created for the Joget deployment.

You can view the deployment in the Workloads page in the GKE console.

Image Modified

Image Modified

In the Services & Ingress page, you can see an External load balancer service with a corresponding Endpoint URL.

Click on that Endpoint URL to access Joget.

Image Modified


5. Setup Database

...

Key in the previously created MariaDB service name in the Database Host, and the root password in the Database Password fields. Click on Save.

Image Modified

Once the setup is complete, click on Done and you will be brought to the Joget App Center.

Image Modified


6. Scale Deployment

...

Key in the required number of replicas (pods) that you require and click on the Scale button.

Image Modified

The desired number of pods will initialize and startup. These instances will have session replication configured, so load can be balanced between them and transparent failover will happen in the event of failure.

Image Modified


Sample Deployment YAML

...