Create a Kubernetes Deployment

Create a Kubernetes Deployment (a .yaml configuration file), which describes how to deploy the Docker image of the TIBCO BPM Enterprise application to the Kubernetes cluster. A sample deployment file is included in the TIBCO BPM Enterprise installation.

Configure Environment Variables

The following describes the parameters in the deployment file.

Parameter Description
name: The name to be used to identify the TIBCO BPM Enterprise container.
image: The name of the Docker image of the TIBCO BPM Enterprise application. By default:

tibco/bpm/runtime:5.0.0

livenessProbe: The definition of the Kubernetes livenessProbe, used to ensure that the container is healthy and responsive. This must be defined using an httpGetAction, with:
  • path defined as /bpm/adapter/v1/liveness.
  • port defined with the same value as containerPort.
readinessProbe: The definition of the Kubernetes readinessProbe, used to determine the container's readiness to accept work. This must be defined using an httpGetAction, with:
  • path defined as /bpm/adapter/v1/readiness.
  • port defined with the same value as containerPort.
ports: Port numbers to be exposed:
  • containerPort: Number of the port to expose on the pod's IP address. By default this is set to 8181.
  • hostPort: Number of the port to expose on the host. By default this is set to 8181.
env: This section must contain the following environment variables, which are used to inject configuration data required by TIBCO BPM Enterprise into the pod:
  • JDBC_URL - The JDBC connection string to connect to the TIBCO BPM Enterprise database.
  • LDAP_NAME_ALIAS - Identifies the LDAP directory.
  • LDAP_NAME_URL - Used to connect to the LDAP directory.
  • JDBC_SSL_CONFIG - This is the SSL configuration for the JDBC connection.
  • LDAP_<GROUP_NAME>_SSLCERT - This is used to configure LDAP SSL.
Use of the following environment variable is optional, but recommended:
  • ADMIN_CRYPTO_KEY - Defines the key used to encrypt and decrypt sensitive data held in the BPM database definition of shared resources (HTTP Clients, Keystore Providers, SSL Client Providers, SMTP Connections, SAML Connections, and OpenID Connections).
    Note: If ADMIN_CRYPTO_KEY is not specified, this data will be stored in the BPM database in unencrypted format.

For more information, see Configure Environment Variables.

For more general information about Docker deployment, see Deployment.