v3.5.2

Coherence Operator Release 3.5.2

• Supported Kubernetes versions: v1.33 v1.32 v1.31 v1.30 v1.29 v1.28 v1.27

• Supported OpenShift versions: v4.15-v4.18

What's Changed

• Update the doc links in README.md by @dhirupandey in #759
• Do not specify a JVM garbage collector if none specified in the Coherence yaml by @thegridman in #760
• FIPS mode changes and docs by @thegridman in #761
• Fixed an issue where the serviceAccount could not be set to "default" by @thegridman in #762
• Update grafana-import.sh script and doco for latest dashboards by @tmiddlet2666 in #765
• Fix links in the Helm chart README.md by @thegridman in #767
• Expose additional fields for port Service spec to support features such as topology based routing by @thegridman in #769

Full Changelog: v3.5.1...v3.5.2

v3.5.1

Coherence Operator Release 3.5.1

• Supported Kubernetes versions: v1.33 v1.32 v1.31 v1.30 v1.29 v1.28 v1.27

• Supported OpenShift versions: v4.15-v4.18

What's Changed

• Add progressDeadlineSeconds to the Operator deployment yaml and Helm … by @thegridman in #752
• Code refactorings and clean up by @thegridman in #754
• TLS cipher suites and FIPS compliance by @thegridman in #755

Full Changelog: v3.5.0...v3.5.1

v3.5.0

Coherence Operator Release 3.5.0

Major Changes

Operator CRD Install

Prior to v3.4.3 the operator would install CRDs when it started. In v3.4.3 the default behaviour was changed to not install CRDs, but it was still possible to change the default and get the operator to install CRDs. In v3.5.0 this option has now been completely removed. The install scripts and Helm chart will install the CRDs, see the installation guide in the documentation for more information. For customers that manually edit install scripts, the CRDs must now be installed or the operator will not start.

This change may impact customers who install the Operator using Helm, because the CRDs from previous install were not managed by Helm. The work around for this is documented in the installation guide.

OpenShift

• The Coherence Operator is now certified to run on OpenShift and is available in the OpenShift Community Operators. The Coherence Operator can be installed on OpenShift using just a few clicks on the OpenShift UI console.

Operator and Coherence Images

• The Coherence Operator binaries and all Coherence Operator images are now built internally in Oracle on the Oracle Coherence engineering team's build infrastructure
• The Coherence Operator install manifests and scripts now use Oracle Container Registry as the default location of the Operator images
• The default Coherence image used by the Operator is the Coherence CE 14.1.2-0-2 image from Oracle Container Registry
• Images are still published to GitHub Container Registry for any customer that wants to pull them from there. The images on GitHub are the same images built internally in Oracle and published to GitHub

Supported Kubernetes Versions

• Tested on Kubernetes versions: v1.33 v1.32 v1.31 v1.30 v1.29 v1.28 v1.27 v1.26

• Tested on OpenShift versions: v4.15-v4.18

What's Changed

• Use Oracle Container Registry as the default image registry by @thegridman in #706
• Provide option to run an image entry point by @thegridman in #707
• bump dependencies and go version by @thegridman in #709
• Add deprecation comments to CRD fields that are deprecated in the underlying APIs by @thegridman in #710
• Use Go 1.24 by @thegridman in #711
• Update federation example by @tmiddlet2666 in #715
• Use Coherence resource generation instead of calculating a hash by @thegridman in #724
• Add polyglot client example by @tmiddlet2666 in #725
• The operator no longer installs the CRDs on start-up by @thegridman in #726
• Add scale sub resource to the Coherence Editor roles by @thegridman in #731
• Use Gimme to automatically install the correct Go version by @thegridman in #735
• Update installation documentation by @thegridman in #733
• Correct gRPC dashboards by @tmiddlet2666 in #738
• Fix minor issue with Makefile in polyglot example by @tmiddlet2666 in #739
• Expose additional StatefulSet and readiness probe fields by @thegridman in #742

Full Changelog: v3.4.3...v3.5.0

v3.4.3

Coherence Operator Release 3.4.3

What's Changed

• Changes to Spring tests to test more Spring versions by @thegridman in #699
• Fix using the Coherence console, QueryPlus and the CLI via kubectl exec by @thegridman in #696
• Zip docs as a release artifact by @thegridman in #698
• Attach bundle to release by @thegridman in #702

Full Changelog: v3.4.2...v3.4.3

v3.4.2

Coherence Operator Release 3.4.2

Istio

This release contains an important bug fix for anyone using Istio.
The previous Operator release was unable to patch a Coherence StatefulSet when Istio is being used as it could not
connect to any of the Coherence Pods to verify the cluster HA status.

What's Changed

• Fix bug where Operator fails to connect to Coherence Pods when using Istio by @thegridman in #691
• Support setting the Lifecycle field on the Coherence container by @thegridman in #692
• Update Istio test versions and Istio docs by @thegridman in #688
• Fix hash code calculation by @thegridman in #687
• Update install docs to remove conntrack references by @thegridman in #689
• Fix issues with Spring fat-jars by @thegridman in #690

Full Changelog: v3.4.1...v3.4.2

v3.4.1

Coherence Operator Release 3.4.1

What's Changed

• Better support for dual-stack Kubernetes clusters by @thegridman in #671
• Minor dashboard updates by @tmiddlet2666 in #673
• Improve IP Monitor documentation by @thegridman in #675
• Bump Coherence versions by @thegridman in #678
• Apply default topology spread constraints by @thegridman in #679
• Removed unused images when starting KinD by @thegridman in #681
• Update dependency versions by @thegridman in #682

Full Changelog: v3.4.0...v3.4.1

v3.4.0

Coherence Operator Release 3.4.0

Major Changes

Coherence Rolling Upgrades

The Operators now allows more control over how rolling upgrades of Coherence deployments are performed. As well as the default one Pod at a time upgrade controlled by the StatefulSet controller, other strategies such as upgrading by all Pods on a Node can be configured. See the Rolling Upgrades documentation

Coherence Metric Names

The Grafana Dashboards in this release expect new format Coherence metric names that no longer have the "vendor" prefix. See the Metrics documentation

Other Changes

• Fix null pointer issue in runner if callback to the Operator fails by @thegridman in #656
• Fix broken Prometheus doc links by @thegridman in #659
• Make support for CoherenceJob resources optional by @thegridman in #660
• Upgrade Grafana dashboards with new metrics and Grafana 10+ support by @tmiddlet2666 in #657
• Apply Helm chart global labels and annotations to all resources in the chart by @thegridman in #662
• Allow additional labels and annotations to be specified for the WKA Service by @thegridman in #667
• Support rolling upgrade by node by @thegridman in #668
• Support more ways to configure Coherence site and rack by @thegridman in #668

Full Changelog: v3.3.5...v3.4.0

v3.3.5

Coherence Operator Release 3.3.5

What's Changed

• Fix #653 - Incorrect usage of COHERENCE_CACHE_CONFIG in example yaml … by @rlubke in #654
• Fix the web-hook to ignore resources with a deletion timestamp set by @thegridman in #655
• Bump golang.org/x/net from 0.21.0 to 0.23.0 by @dependabot in #648
• Upgrade dashboards to use newer panels by @tmiddlet2666 in #650
• Remove stale documentation links by @vasac in #651

Full Changelog: v3.3.4...v3.3.5

v3.3.4

Coherence Operator Release 3.3.4

What's Changed

• Bump google.golang.org/protobuf from 1.31.0 to 1.33.0 by @dependabot in #646
• Allow resource limits to be set for the Operator's init container by @thegridman in #647
• Make sure labels are consistent on RBAC resources

Full Changelog: v3.3.3...v3.3.4

v3.3.3

Coherence Operator Release 3.3.2

What's Changed

• Add federation retries to federation details dashboard. Other minor u… by @tmiddlet2666 in #638
• Update member details dashboard to show heap and heap after GC by @tmiddlet2666 in #640
• Set O/S platform and architecture for images by @thegridman in #641
• Allow global labels and annotations to be specified by @thegridman in #643
• Bump k8s to 1.29, Go to 1.22 and various dependency versions by @thegridman in #644

Full Changelog: v3.3.2...v3.3.3