...

• Deployment of JS7 Components: js7-deployment.yaml
• Values for Kubernetes JS7 deployment file: js7-service.yaml

...

Introduction

• JS7 can be set up for use with a Helm Chart. Using the Linux-based JS7 images for Docker® containers which ship with a current Alpine base image and OpenJDK.
  • Docker® images for JS7 are publicly available from https://hub.docker.com/r/sosberlin/js7.
  • Deploying containers using Kubernetes Cluster is publicly available from JS7 - How to deploy to a Kubernetes Cluster.
  • Instructions on how to run containers for JS7 components can be found in the JS7 - Installation for Docker Containers article series.
• Users deploy JS7 components by creating a Kubernetes deployment object from a deployment YAML file.
  • For this purpose, users have to first install and set up the Kubernetes Cluster see JS7 - How to install a Kubernetes Cluster.
  • With the Helm Chart being up and running users can use values YAML files to deploy JS7 components.

...

The YAML file describes a single Pod for deployment to Kubernetes which is a group of one or more containers and a ConfigMap. The Pod includes three containers:

1. The js7joc container runs the joc-2-5-1 image and exposes port 4446. It uses a ConfigMap with the name hibernate-config to specify a volume mounted to the /var/sos-berlin.com/js7/joc/resources/joc directory.
2. The js7con container runs the controller-2-5-1 image and exposes port 4444.
3. The js7agent container runs the agent-2-5-1 image and exposes port 4445.

The following implications apply:

• Each container runs a different image from the sosberlin/js7 repository and is assigned a unique port.

• For the js7joc container the volumeMounts element specifies the hibernate-config ConfigMap which is mounted to the /var/sos-berlin.com/js7/joc/resources/joc directory.

...