Skip to content

v3.0.2
Compare
Choose a tag to compare
@thegridman thegridman released this 12 Aug 09:30
v3.0.2
3f6d6eb

This is a minor point release of the Coherence Operator.

Fixes

  • Fixed an issue where the Operator continually re-reconciled the StatefulSet for a Coherence deployment is persistence was enabled using PVCs.

Notes When Using Persistence or Configuring VolumeClaimTemplates

One of the limitations of a StatefulSet (which is used to control the Pods of a Coherence deployment) is that certain fields are effectively read-only once the StatefulSet has been created. One of these is the VolumeClaimTemplates array. This means that the Coherence Operator will not attempt to change a VolumeClaimTemplate for a StatefulSet once the StatefulSet has been created even if a change to a Coherence deployment yaml should have caused a change. For example enabling and then later disabling persistence will not cause the persistence VolumeClaimTemplate to be removed from the StatefulSet, and vice-versa, enabling persistence as an update to a running deployment will fail to add the VolumeClaimTemplate.

Images

Images can be pulled from Oracle Container Registry (credentials are not required to pull the Operator images).

docker pull container-registry.oracle.com/middleware/coherence-operator:3.0.2
docker pull container-registry.oracle.com/middleware/coherence-operator:3.0.2-utils
Assets 2
Loading