v2.1.0

NOTE

We are aware that this version of the Operator contains changes to the CRD that make it incompatible with previous versions. What this means is that if version 2.1.0 of the Operator is installed into a k8s namespace that already contains CoherenceCluster instances deployed with a previous version this causes error messages in the Operator and the existing clusters can no longer be controlled by the Operator. The only solution is to remove and re-create the affected clusters.

New Features

• Add the ability to specify role start-up dependencies for a cluster. Roles can be configured to start after other roles. https://oracle.github.io/coherence-operator/docs/2.1.0/#/clusters/035_role_startup_ordering

• Allow roles to be configured to not be part of the cluster's WKA list. https://oracle.github.io/coherence-operator/docs/2.1.0/#/about/05_cluster_discovery

v2.0.5

Fixes:

• Disable Flight Recorder if the Coherence image is not running a HotSpot JVM

• Issue #379 Coherence fails to start in OpenShift.
  Whilst this issue has been fixed there are still issues where the existing Coherence images fail on OpenShift due to file permissions in the image. The images have an oracle user that owns the Coherence installation directories but OpenShift runs the containers with a random user. This will likely be fixed in future Coherence images but in order to make existing images work:

1. Ensure the anyuid security content is granted
2. Ensure that WebLogic containers are annotated with openshift.io/scc: anyuid

For example, to update the OpenShift policy, use:

$ oc adm policy add-scc-to-user anyuid -z default

and add the openshift.io/scc annotation to the CoherenceCluster For example:

kind: CoherenceCluster
metadata:
  name: test-cluster
spec:
  annotations:
    openshift.io/scc: anyuid
roles:
  - role: storage

v2.0.3

Potential fix for issue #371

v2.0.2

Fixes:
Issue #368
It appeared that some older versions of kubectl could not scale a CoherenceRole that did not have a specific replicas value set.

[Issue #367]
A bug in the coherencerole_controller caused it to corrupt the CoherenceRole spec if values such as jvm.args were specified at the default level and for a specific role.

v2.0.1

Fixes:
Issue 365
Add additional network and DNS configuration options to the CRD. See the related documentation here
https://oracle.github.io/coherence-operator/docs/2.0.1/#/clusters/095_networking

Issue 364
Fixed an issue where JVM args were being corrupted if they were specified at both the default level and for a specific role if creating a cluster with explicit roles defined.