v21.6.2

Following the upgrade to IBM MQ 9.2 in release v21.6.1, the below list of breaking changes has been introduced:
- On existing deployments, the upgrade of IBM MQ requires the applications pods to be scaled down completely, followed by a delay to process any remaining messages, before updating the deployment
- Moved global.mq.multiInstance.availabilityType to global.mq.availabilityType
- Moved global.mq.multiInstance.storageType to global.mq.storageType
- Moved global.mq.multiInstance.storageClassName to global.mq.storageClassName
- Removed global.mq.multiInstance as a configuration, and the following children parameters:
  - operatorsEnabled, cephEnabled, useDynamicProvisioning, nfsEnabled, nfsIP, nfsFolder, nfsMountOptions
- Support for manual creation of persistent volumes and persistent volume claims has been removed
Removed global.apps.common.persistence.subDir as a configuration
- The paths on the storage volume have now change from <root>/<HelmRelease_or_subDir>/<podName> to <root>/<podName>. This is to accommodate pod initialization on start-up
Ingress and IngressClass resources have graduated to networking.k8s.io/v1, see Ingress graduates to General Availability
- Due to ingress graduating to networking.k8s.io/v1 spm ingress.yaml has been update to check networking.k8s.io version.
- Definition of the ingress path has been moved to the spm.ingress.item template

Configure PodMonitor resources for the apps producer and consumers pods and for the mqserver metrics pods to integrate with OpenShift's built-in Prometheus or Prometheus Operator

The following helm-charts have been updated to chart version 21.6.2: apps, batch, mqserver, spm, uawebapp, web, xmlserver.
Changed DB2 datasources isolation level for the apps producer and consumers pods. See Transaction control/Underlying design/DB2/Repeatable Read

Fixed issue where tuning params for resources on MQ pods created by the MQ operator were not being honoured

Provide feedback