JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 13

changes.mady.by.user Kanika Agrawal

Saved on

compared with

New Version 14

changes.mady.by.user Andreas Püschel

Saved on

Key

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

...

  • JS7 can be set up for use with a Kubernetes Cluster. Using the Linux based JS7 images for Docker® containers which ship with a current Alpine base image and OpenJDK.
  • Users deploy JS7 components by creating a Kubernetes deployment object from a deployment YAML file.
    • To this purpose users have to first install and set up the Kubernetes Cluster see JS7 - How to install a Kubernetes Cluster.
    • With the Kubernetes Cluster being up and running users can use YAML deployment files to deploy JS7 components.

...

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

  • Each container defines environment variables which control a number of runtime parameters for the application such as:

    • RUN_JS_JAVA_OPTIONS : see JS7 - FAQ - Which Java Options are recommended
    • RUN_JS_USER_ID: specifies the numeric User ID and Group ID - separated by a colon - of the run-time account used for the related JS7 component. A value 0:0 indicates the root account and root group, a value 1000:1000 specifies a user account with the given User ID and Group ID. For details see JS7 - Running Containers for User Accounts.
    • RUN_JS_ID: specifies the Controller ID which is a unique identifier for a Standalone Controller or Controller Cluster.

  • 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.

...