![[OpenShift Container Platform]](ngocp.gif)
![[Continuous Delivery]](ngcd.gif)
![[Amazon EKS]](ngeks.gif)
![[IBM MQ Advanced]](ngadv.gif)
![[IBM Cloud Pak for Integration]](ngcp4i.gif)
Support for the IBM MQ Operator
The IBM® MQ Operator is supported as part of IBM MQ, IBM MQ Advanced, and IBM Cloud Pak® for Integration
Supported platforms
The IBM MQ Operator is supported on Red Hat® OpenShift® Container Platform and, from IBM MQ Operator 3.9.0, Amazon EKS
- Releases of Red Hat OpenShift Container Platform are no longer supported by IBM MQ after Red Hat stops support. See Red Hat OpenShift Container Platform Life Cycle Dates for more details.
- Releases of Amazon EKS are no longer supported by IBM MQ after Amazon stops both standard and extended support. See Understand the Kubernetes version lifecycle on EKS for more details.
Supported CPU architectures
The IBM MQ Operator is supported onamd64 and s390x z/Linux, and on
ppc64le
Power® Systems version 9 and above. Note that all nodes in
a Red Hat OpenShift or Amazon EKS cluster must use the same CPU
architecture. Duration of support
IBM provides defect and usage support for the IBM MQ Operator and the associated queue manager images. The duration of support depends on which license you use:
- If you use an IBM Cloud Pak for Integration license, then the
IBM MQ Operator is supported for the same duration as the
corresponding IBM Cloud Pak for Integration version. Some versions are
IBM Cloud Pak for Integration - Support Cycle 2 (formerly Long Term Support) and others are Continuous Delivery (CD). The CD operator and queue managers are
supported until next IBM Cloud Pak for Integration CD or CP4I-LTS release. The CP4I-LTS operator and queue managers deployed with the
IBM Cloud Pak for Integration license are supported until the next CP4I-LTS release, plus a grace period to allow for
upgrade.
For example, if you create a queue manager using the IBM Cloud Pak for Integration license “L-JTPV-KYG8TF”, that is associated with a CP4I-LTS release. That will deploy IBM MQ Advanced 9.4.0, and will be supported in line with that IBM Cloud Pak for Integration version (two years).
- If you use an IBM MQ Advanced or an IBM MQ license, only the IBM MQ Continuous Delivery stream is supported. Each IBM MQ Operator and queue manager deployed with an IBM MQ Advanced or IBM MQ license is supported for one year from the first operator which supports that queue manager version. Releases pro-actively receive security fixes until the next Continuous Delivery release. For example, if you create a queue manager using the IBM MQ Advanced license “L-EHXT-MQCRN9”, it will be using IBM MQ Advanced 9.4.0 as a Continuous Delivery release, and will be supported for one year, and security fixes will be published until the release of IBM MQ 9.4.1. After the release of version 9.4.1, on request IBM will assess the feasibility of making reasonable efforts to provide a fix on the previous CD release level
Fix availability
Periodic and interim queue manager fixes are available from IBM Container Registry. Interim fixes for the IBM MQ Operator are not available.Unavailable features
The following features of IBM MQ Advanced are not available for queue managers operated by the IBM MQ Operator:- Replicated Data Queue Managers (RDQM) are not available - this feature is tightly coupled with the Linux kernel, so it not supported in containers
- Linear logging for queue managers is not available
- Specifying custom command line options for crtmqdir, crtmqm, strmqm and endmqm are not available — Most options can be configured using an INI file, however some cannot be configured, such as the use of linear logging.
- Operating system (OS) users are not available
- AMQP is not installed
- MQTT is not installed
- Managed File Transfer agent is not available. However, you can use the IBM MQ Operator to provide one or more Coordination, Command, or Agent queue managers.
- Advanced Message Security with MCA interception using a separate key store is not available. MCA interception can still be configured to use the main queue manager key store.
You can only use the queue manager container images supplied by IBM with the MQ Operator, and cannot build your own image with custom code. The exception to this is to add a container image layer to an IBM-supplied image, in order to add configuration files or exits.