v3.2.8

Coherence Operator Release 3.2.8

Note: Operate Image Changes

This release changes the images used to run the Operator. Previously, the Operator releases published two images, ghcr.io/oracle/coherence-operator:3.2.7 and ghcr.io/oracle/coherence-operator-utils:3.2.7. From this release, there will be only a single image ghcr.io/oracle/coherence-operator:3.2.8 which contains the combined binaries from both previous images. This will greatly simplify managing Operator images, especially for customers that need to copy and deploy images to their own registries. Anywhere in Coherence deployments where the previous coherence-operator-utils was used can just be replaced with the coherence-operator image. This image change does not break backwards compatibility or the ability to upgrade the Operator while Coherence clusters are running.

Changes

#552 Reject changes that would create an invalid StatefulSet patch

#551 Add tests to verify links in documentation

#550 Update K8s test versions

#549 Properly support images using Coherence 14.1.1.2206 or CE 22.06 and higher using Java 17

#548 Properly detect which Coherence main class to run when using Coherence 14.1.1.2206 or CE 22.06 and higher

#547 Members Grafana Dashboard should use coherence_memory_heap_after_gc_used

#546 Correct detection of Coherence 22.06

#545 Document the fact that G1GC is experimental if using ARM64 Java 8 JVMs in Coherence images

#544 Add securityContext to the Operator Helm chart

#543 Produce only a single Operator image

#542 Update Coherence certification version and add test using Graal based Coherence images

#541 Add Coherence*Extend example

#540 Remove default cpu limits for Coherence Pods

#539 Ensure certification tests use imagePullSecrets from the test environment

#538 Update docs to specify recommended Grafana versions