v3.2.0

Coherence Operator Release 3.2.0

The version of the Coherence Operator no longer supports running on Kubernetes clusters prior to 1.16

⚠️ The Helm chart for this version has breaking changes that means the helm upgrade command cannot be used to upgrade a 3.1.5 or earlier Operator deployment to 3.2.0. This has been fixed in v3.2.1, which means that helm upgrade cannot be used to upgrade from 3.2.0 to 3.2.1, but can be used to upgrade 3.1.5 or earlier to 3.2.1.

Changes and Enhancements

• Added support for running in Kubernetes on Linux/arm64 The Operator images are multi-arch images, so the correct image corresponding to the platform architecture will be used. The caveat is that the Coherence application image used to run Coherence clusters must also support ARM
• The Coherence IPMonitor is disabled by default in Coherence clusters managed by the Coherence Operator
• Upgraded the version of the Operator SDK used by this project to v1.7.2 with a corresponding bump in Kubernetes API used.
• Added documentation on running Coherence clusters with Istio
• Upgrade to Operator SDK 1.9.0 and Go 1.16
• The default Coherence image used to deploy Coherence clusters is version 21.06

Fixes

• Further hardened rolling upgrade when there is only a single Coherence storage member
• Improved the readiness probe to remove needless checks for storage disabled members