Chapter 8. Upgrading a template-based broker deployment

Procedure

1. Navigate to the OpenShift Container Platform web console and log in.
2. Click the project in which you want to upgrade a non-persistent broker deployment.

3. Select the Deployment Config (DC) corresponding to your broker deployment.

   1. In OpenShift Container Platform 4.1 or later, click Workloads Deployment Configs.
   2. In OpenShift Container Platform 3.11, click Applications Deployments. Within your broker deployment, click the Configuration tab.

4. From the Actions menu, click Edit Deployment Config (OpenShift Container Platform 4.1 or later) or Edit YAML (OpenShift Container Platform 3.11).

   The YAML tab of the Deployment Config opens, with the .yaml file in an editable mode.

5. Edit the image attribute to specify the latest AMQ Broker 7.7 container image, registry.redhat.io/amq7/amq-broker:7.7.

6. Add the imagePullSecrets attribute to specify the image pull secret associated with the account used for authentication in the Red Hat Container Registry.

   Changes based on the previous two steps are shown in the example below:

   ...
   spec:
       containers:
           image: 'registry.redhat.io/amq7/amq-broker:7.7'
   ..
   imagePullSecrets:
     - name: {PULL-SECRET-NAME}

   Note

   In AMQ Broker, container image tags increment by 1 for each new version of the container image added to the Red Hat image registry, for example, 7.7-1, 7.7-2, and so on. If you specify a tag name without a final digit (7.7, for example), this tag is known as a floating tag. When you specify a floating tag, OpenShift Container Platform automatically identifies the most recent available image (that is, the image tag with the highest final number) and uses this image to upgrade your broker deployment.

7. Click Save.

   If a newer broker image than the one currently installed is available in the Red Hat Container Registry, OpenShift Container Platform upgrades your broker deployment. To do this, OpenShift Container Platform stops the existing broker Pod and then starts a new Pod that uses the new image.

Procedure

1. Navigate to the OpenShift Container Platform web console and log in.
2. Click the project in which you want to upgrade a persistent broker deployment.

3. Select the StatefulSet (SS) corresponding to your broker deployment.

   1. In OpenShift Container Platform 4.1 or later, click Workloads Stateful Sets.
   2. In OpenShift Container Platform 3.11, click Applications Stateful Sets.

4. From the Actions menu, click Edit Stateful Set (OpenShift Container Platform 4.1 or later) or Edit YAML (OpenShift Container Platform 3.11).

   The YAML tab of the StatefulSet opens, with the .yaml file in an editable mode.

5. To prepare your broker deployment for upgrade, scale the deployment down to zero brokers.

   1. If the replicas attribute is currently set to 1 or greater, set it to 0.
   2. Click Save.
6. When all broker Pods have shut down, edit the Stateful Set .yaml file again. Edit the image attribute to specify the latest AMQ Broker 7.7 container image, registry.redhat.io/amq7/amq-broker:7.7.

7. Add the imagePullSecrets attribute to specify the image pull secret associated with the account used for authentication in the Red Hat Container Registry.

   Changes based on the previous two steps are shown in the example below:

   ...
   spec:
       containers:
           image: 'registry.redhat.io/amq7/amq-broker:7.7'
   ..
   imagePullSecrets:
     - name: {PULL-SECRET-NAME}

8. Set the replicas attribute back to the original value.

9. Click Save.

   If a newer broker image than the one currently installed is available in the Red Hat Container Registry, OpenShift Container Platform upgrades your broker deployment. To do this, OpenShift Container Platform restarts the broker Pod.