Red Hat OpenShift Container Platform 4.6 and above
IBM Cloud Pak foundational services versions
IBM Cloud Pak foundational services 3.8 and above (v3
channel)
What's new
Adds status conditions for deprecated IBM® MQ
versions.
What's changed
Images moved from Docker Hub to IBM Container Registry.
Customers with firewall rules might need to adjust them to access the images on IBM Container Registry.
Airgap customers experience a node restart when upgrading to IBM MQ Operator 1.8.0.
Deprecated versions: IBM MQ 9.1.5, 9.2.0 CD, 9.2.1,
9.2.2. These versions might not be reconciled by future versions of the IBM MQ Operator.
Changes to license logic: Customers upgrading to IBM MQ 9.2.5 may use only the licenses specified to work with
IBM MQ 9.2.5. See Licensing reference for mq.ibm.com/v1beta1.
Vulnerabilities that are addressed are detailed in this Security
Bulletin.
Red Hat OpenShift Container Platform 4.6 and above
IBM Cloud Pak foundational services versions
IBM Cloud Pak foundational services 3.7 and above
(v3 channel)
What's new
Adds IBM MQ 9.2.3 as a
continuous delivery release (amd64 only for IBM Cloud Pak for Integration 2021.2.1; amd64 or
s390x when using an IBM MQ
license)
New type of availability for queue managers: Native HA. Available for production use, as part of
IBM Cloud Pak for Integration 2021.2.1.
Red Hat OpenShift Container Platform 4.6 and above
IBM Cloud Pak foundational services versions
IBM Cloud Pak foundational services 3.7 and above
(v3 channel)
What's new
Adds IBM MQ 9.2.2 as a
continuous delivery release (amd64 only for IBM Cloud Pak for Integration 2021.1.1; amd64 or
s390x when using an IBM MQ
license)
New type of availability for queue managers: Native HA. Available for evaluation purposes only, as part
of IBM Cloud Pak for Integration 2021.1.1.
Integration with Red Hat OpenShift Container Platform
Cluster Monitoring for Prometheus metrics, by providing a ServiceMonitor
resource
What's changed
The IBM Licensing Operator is no longer created by default when you create a queue manager
Updates to multi-instance queue managers are now handled in a rolling order.
As part of this change, a Kubernetes startup probe has been introduced that affects the values used
when configuring the liveness probe. The startup probe starts immediately, then waits for the queue
manager to start successfully. If the startup probe passes at any time within this wait period, the
liveness and readiness probes then start. Previously, if you had a queue manager that was slow to
start, you might have increased the initialDelaySeconds setting on the liveness
probe. If you did this, you should now revert initialDelaySeconds to the earlier
setting.
The CustomResourceDefinition is upgraded from apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1
Known issues and limitations
Requires IBM Cloud Pak foundational services 3.7, which
contains an incompatible change in the Identity and Access Management (IAM) component. If you have
any queue managers that use an IBM Cloud Pak for Integration license, then
after this upgrade, a queue manager restart will be required to access the web console, and you will
also see other errors logging into the web console. You can fix these errors by upgrading to the
latest value of .spec.version for your chosen IBM MQ version, after the operator
upgrade is complete.
Rolling update does not automatically start if you are upgrading the MQ version. You need to manually delete the pods.
IBM MQ Operator 1.4.0
IBM Cloud Pak for Integration version
IBM Cloud Pak for Integration 2020.4.1 (IBM MQ Operator 1.4.0 is a CD release, and not eligible for Extended
Update Support)
Red Hat OpenShift Container Platform 4.6 and above
What's new
Adds IBM MQ 9.2.1 as a
continuous delivery release
You can now prevent the creation of the default queue manager Route by setting .spec.queueManager.route.enabled to false
Known issues and limitations
When updating a QueueManager with an availability type of
MultiInstance, both Pods will be deleted immediately. They should both be restarted
quickly by Red Hat OpenShift Container Platform.
IBM Cloud Pak foundational services 3.6 (stable-v1
channel)
What's new
Extended Update Support (EUS) is offered for .spec.version
fields ending with -eus, when using a IBM Cloud Pak for Integration license
Adds a new way of setting labels and annotations on the QueueManager resource
using .spec.labels and .spec.annotations
What's changed
Improves error handling when trying to change from single-instance to multi-instance
Improvements to how the QueueManager properties are rendered in
the IBM Cloud Pak for Integration Platform Navigator, and the Form View of the Red Hat OpenShift Container Platform web console
Fixes the default license metric when using a IBM Cloud Pak for Integration license, to be
VirtualProcessorCore
Fixes the Resources tab for QueueManager
in the Red Hat OpenShift Container Platform web console, which now correctly shows
the resources managed by the IBM MQ Operator for that queue
manager
Known issues and limitations
When updating a QueueManager with an availability type of
MultiInstance, both Pods will be deleted immediately. They should both be restarted
quickly by Red Hat OpenShift Container Platform.
Adds additional runtime checks to prevent the use of invalid storage classes. For more
information, see Disabling runtime webhook checks
Simplifies experience for multi-instance queue managers: this can now be chosen with just one
property (.spec.queueManager.availability.type) in the
QueueManager resource
Simplifies choosing a non-default Storage Class, by introducing the
.spec.queueManager.storage.defaultClass property in the
QueueManager resource
What's changed
Improvements to how the QueueManager properties are rendered in
the IBM Cloud Pak for Integration Platform Navigator, and the Form View of the Red Hat OpenShift Container Platform web console
If an upgraded queue manager version is available, it will now be flagged in the
IBM Cloud Pak for Integration Platform Navigator
Support for MQ Native HA for
production use, when used with a IBM Cloud Pak for Integration license. Note
that queue managers using Native HA under an evaluation license with IBM MQ 9.2.2 cannot be upgraded to 9.2.3. The evaluation period
has ended.
Fixes issue with single sign-on with IBM Cloud Pak foundational services 3.7 and higher, which is needed only when migrating from
an EUS release to a CD release.
Fixes issue with liveness probe (chkmqhealthy) and readiness probe (chkmqready) when running under SecurityContextContraints which allow privilege escalation.
![[OpenShift Container Platform]](ngocp.gif)
![[Extended Update Support]](ngeus.gif)
![[Continuous Delivery]](ngcd.gif)
![[IBM Cloud Pak for Integration]](ngcp4i.gif)