[Continuous Delivery][IBM MQ Advanced][V9.1.4 Dec 2019][Linux]

Deploying a queue manager using the Helm CLI

Use Helm to deploy a queue manager onto a Red Hat® OpenShift® Container Platform cluster. This task should be completed by a project administrator.

Before you begin

You need to install Helm V2 and the Red Hat OpenShift Container Platform command-line interface. If you're not using IBM Cloud Pak® for Integration, then follow the steps for Preparing your OpenShift cluster for IBM MQ on OpenShift using Helm.

Log into your cluster using cloudctl login (for IBM Cloud Pak for Integration), or oc login.


  1. Ensure that you've added the IBM Helm repository to your local copy of Helm.
    For example, you can run the following command:
    helm repo add ibm-entitled-charts https://raw.githubusercontent.com/IBM/charts/master/repo/entitled
  2. Review the configuration options for your queue manager

    The deployment step includes both installation and configuration steps. Some settings for your queue manager must be set at deployment time, and changing them requires a re-deployment.

    You can view the Helm chart README for details of all the available deployment options, by running one of the following commands:
    • For IBM® MQ Advanced certified container in IBM Cloud Pak for Integration:
      helm inspect readme ibm-entitled-charts/ibm-mqadvanced-server-integration-prod
    • For IBM MQ Advanced certified container:
      helm inspect readme ibm-entitled-charts/ibm-mqadvanced-server-prod
    You will typically need at least the following parameters:
    1. Release name. For example: my-release
    2. Remote Helm repository. For example: ibm-entitled-charts
    3. Helm chart: for example ibm-mqadvanced-server-prod or ibm-mqadvanced-server-integration-prod
    4. Image pull secret name. For example: entitled-registry. Note this is not needed if you are deploying into the pre-defined project for MQ in IBM Cloud Pak for Integration
  3. Deploy a queue manager.

    Note that by default, the Helm chart assumes that you have a default Storage Class set in your Red Hat OpenShift Container Platform cluster.

    For example, to install a basic queue manager in IBM Cloud Pak for Integration, run the following command:
    helm install \
    --tls \
    --name my-release \
    ibm-entitled-charts/ibm-mqadvanced-server-integration-prod \
    --set license=accept \
    --set tls.hostname=my.cluster \
    --set tls.generate=true
    You can enter any hostname in the tls.hostname field (this is a required field but will not be used as in this example we are generating a new self-signed certificate)
    To install a basic queue manager independently of IBM Cloud Pak for Integration, you could run the following command:
    helm install \
    --name my-release \
    ibm-entitled-charts/ibm-mqadvanced-server-prod \
    --set license=accept \
    --set image.pullSecret=ibm-entitlement-key