Page History

...

Download the archive file:  buildachart_js7_workingworking.zip

The archive includes the following files.

...

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.

...

1. Download the archive file: buildachart_js7_workingworking.zip. Open a console window from the directory where you downloaded the .zip archive and extract the archive.
   
   
   

2. Execute the below command to deploy working charts using the helm install command. We can do a dry-run of a helm install and enable debug to inspect the generated definitions.The service.internalPort value is used here to ensure that the Service and Deployment objects work together correctly.

   helm install buildachart_js7_working --dry-run --debug ./buildachart_js7_working --set service.internalPort=4446

   
   
   

3. Run the below command to run the pods on the internal port.

   helm install js7 ./buildachart_js7_working --set service.type=NodePort

...