Chapter 4. Upgrading AMQ Broker on OpenShift Container Platform


To upgrade AMQ Broker on OpenShift Container Platform, you must have an existing broker deployment, similar to those described in Deploying a basic broker and Tutorials.

4.1. Upgrading non-persistent broker deployments

The procedure in this section shows you how upgrade a non-persistent broker deployment. In the previous version of AMQ Broker, the non-persistent broker templates in the OpenShift Container Platform service catalog were labeled as follows:

  • Red Hat AMQ Broker 7.2 (Ephemeral, no SSL)
  • Red Hat AMQ Broker 7.2 (Ephemeral, with SSL)
  • Red Hat AMQ Broker 7.2 Custom Config (Ephemeral, no SSL)

Prerequisites

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. In the Deployment Config section of your broker deployment, click Edit.

    The Edit Deployment Config page opens.

  4. In the Deployment Strategy section, in the Strategy Type drop-down list, select Rolling.
  5. In the Images section, specify an Image Stream Tag as follows.

    1. In the Namespace drop-down list, select the project namespace in which you installed your AMQ Broker 7.3 image.
    2. In the Image Stream drop-down list, select the AMQ Broker 7.3 on OpenShift Container Platform image stream, amq-broker-73-openshift.
    3. In the Tag drop-down list, select a tag for the image to which you want to upgrade. To specify the latest available version, select latest. Otherwise, select a specific image version.

      Note

      In AMQ Broker 7.3, image tags follow the naming convention 7.3-1, 7.3-2, and so on. These numbers increment by 1 for each new version of the image added to the Red Hat image registry. In the Tag drop-down list, if you specify a tag of 7.3, this tag is known as a floating tag. When you specify a floating tag, OpenShift Container Platform automatically identifies the most recent image available in your specified project namespace (that is, the 7.3 image with the highest final number) and uses this image to upgrade your broker deployment.

  6. Click Save.

    Based on your selection of a rolling upgrade strategy, if you select an image that is newer than the one currently installed, OpenShift Container Platform automatically upgrades your broker deployment. To do this, OpenShift stops the existing pod and then starts a new pod that uses the new broker container image.

4.2. Upgrading persistent broker deployments

The procedure in this section shows you how to upgrade a persistent broker deployment. In the previous version of AMQ Broker, the persistent broker templates in the OpenShift Container Platform service catalog were labeled as follows:

  • Red Hat AMQ Broker 7.2 (Persistence, clustered, no SSL)
  • Red Hat AMQ Broker 7.2 (Persistence, clustered, with SSL)
  • Red Hat AMQ Broker 7.2 (Persistence, with SSL)

Prerequisites

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. In the Stateful Set section of your broker deployment, click Edit YAML.

    The Edit Stateful Set page opens with your YAML file in an editable mode.

  4. Edit the image attribute to reference an AMQ Broker 7.3 image tag in the Red Hat image registry, as shown below:

    ...
    image: 'registry.redhat.io/amq-broker-7/amq-broker-73-openshift:7.3'
    ...
    Copy to Clipboard Toggle word wrap
    Note

    If you have a scaledown controller configured in your project namespace, the YAML file for your StatefulSet contains an embedded template representing the scaledown controller. This template is labeled statefulsets.kubernetes.io/drainer-pod-template. The scaledown controller template also contains an image attribute that you must update to reference the new broker image version. Edit this additional image attribute exactly as shown in the preceding step.

  5. To ensure that you have at least one running pod, set the replicas attribute to a value of 1 or greater, as shown below.

    Expand
    If replicas is currently set to…​Do this…​

    0

    Set replicas to a value of 1 or greater.

    1 or greater

    1. Set replicas to 0.
    2. Click Save.
    3. Set replicas back to the original value.
  6. Click Save.

    If you specified an image that is newer than the one currently installed, OpenShift Container Platform automatically initiates an upgrade by stopping the existing pod and then starting a new one for the upgraded broker deployment.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top