Example: Supplying additional environment variables for a queue manager

This example deploys a queue manager with two additional environment variables. These environment variables are set on the IBM® MQ container.

About this task

Additional environment variables can be supplied when a queue manager is deployed. This allows the setting of environment variables that are not already exposed by the IBM MQ Operator.

Example

The following example deploys a queue manager with two additional environment variables. These environment variables are set on the IBM MQ container.

Note: The following YAML uses an IBM MQ Advanced license, though you can also use an IBM MQ license. For more information, see Configuring Queue Managers with IBM MQ license annotations by using the IBM MQ Operator.

Important: If you accept the IBM MQ Advanced license agreement, change accept: false to accept: true. See mq.ibm.com/v1beta1: Current license versions for details on the license.

Example QueueManager for Red Hat® OpenShift®

Deploy your queue manager with the following configuration, using the command line or using the Red Hat OpenShift Container Platform web console.

apiVersion: mq.ibm.com/v1beta1
kind: QueueManager
metadata:
  name: env-qm
spec:
  version: 10.0.0.0-r1
  license:
    accept: false
    license: L-CXDB-XTZ9J8
    use: Production
  queueManager:
    env:
    - name: TEST_ENV_1
      value: "true"
    - name: TEST_ENV_2
      value: "false"
    storage:
      queueManager:
        type: ephemeral

Example QueueManager for Amazon EKS

Deploy your queue manager with the following configuration on an Amazon EKS cluster.

apiVersion: mq.ibm.com/v1beta1
kind: QueueManager
metadata:
  name: env-qm
spec:
  version: 10.0.0.0-r1
  license:
    accept: false
    license: L-CXDB-XTZ9J8
    use: Production
  queueManager:
    env:
    - name: TEST_ENV_1
      value: "true"
    - name: TEST_ENV_2
      value: "false"
    storage:
      queueManager:
        type: ephemeral
    route:
      enabled: false
    metrics:
      serviceMonitor:
        enabled: false
  web:
    enabled: false
    route:
      enabled: false

spec.queueManager.route.enabled, spec.queueManager.metrics.serviceMonitor.enabled, and spec.web.route.enabled are set to false because these are Red Hat OpenShift specific features that are enabled by default. These features must be disabled explicitly on Amazon EKS.

Additional information:

If you specify an environment variable that would otherwise have been set by the IBM MQ Operator, this might lead to unpredictable behavior. In this scenario, a warning status condition is added to your QueueManager.