This file has been truncated. show original
##### Thomas Schwade - November 20, 2018
## Running Natural Ajax in a Kubernetes Cluster
### Why Kubernetes?
In a [previous article](https://github.com/zerodrive/NJX-Docker) I have shown how a Natural Ajax web application can be packaged and deployed in a Docker container. The logical next step to leverage this approach is running the application in a Kubernetes cluster. Why? The answer is **scalability**. In an application based on Natural Ajax, Natural and Adabas it is rarely the Natural and Adabas backend that forms the performance bottleneck. More often it is either the browser frontend or the web frontend application. A Kubernetes cluster allows adding and removing instances of the web frontend application as needed and makes that part of the application arbitrarily scalable.
### Setting up a Kubernetes cluster
In order to use Kubernetes it is not necessary to run the application in a private cloud or even under a public cloud provider like AWS, Azure or GCE. Setting up a local Kubernetes cluster on "bare metal" or on a set of Linux virtual machines is more instructive and forms a lower hurdle for many organizations.
For this example I assume that we have already set up a small Kubernetes cluster consisting of one master node and one slave node. Additionally, we have set up a private Docker registry from which the cluster loads the Docker images. In one of the next postings I am going to describe step by step how this infrastructure was set up.
### Verifying the master node and the slave node
First we have a look on the master node and check the cluster is up and running: