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:
- Ensure the anyuid security content is granted
- 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