v2.1.1

Changes

• Allow the scheme to be specified for the fluentd logging configuration.
  When deploying the Operator Helm chart with an Elasticsearch server that requires https the scheme can now be specified. See https://oracle.github.io/coherence-operator/docs/2.1.1/#/logging/030_own

• As an alternative to using host/port/scheme when specifying the Elasticsearch endpoint that fluentd should be configured to use it is now possible to specify the full host URL (or a comma delimited list of URLs) see https://oracle.github.io/coherence-operator/docs/2.1.1/#/logging/030_own

NOTE

If upgrading from earlier releases of the Operator into a k8s namespace where there are already existing Coherence clusters that are configured with Fluentd enabled then due to limitations in the way that the Operator uses Helm internally this release will cause a rolling upgrade of those existing cluster. Existing Coherence clusters that do not have Fluentd enabled will not be affected