The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
The Oracle Coherence Operator simplifies management of Coherence clusters in Kubernetes
Oracle enables organizations using Coherence to move their clusters into the cloud, by supporting industry standards, such as OCI containers and Kubernetes, Oracle facilitates running Coherence on cloud-neutral infrastructure. In addition, Oracle provides an open-source Coherence Operator, which implements features to assist with deploying and managing Coherence clusters in a Kubernetes environment.
The Coherence Operator is a Kubernetes Operator that is used to manage Oracle Coherence clusters in Kubernetes. The Coherence Operator takes on the tasks of that human DevOps resource might carry out when managing Coherence clusters, such as configuration, installation, safe scaling, management and metrics.
The Coherence Operator is a Go based application built using the Operator SDK. It is distributed as a Docker image and Helm chart for easy installation and configuration.
Using the Coherence Operator to manage Coherence clusters running in Kubernetes has many advantages over just deploying and running clusters with the resources provided by Kubernetes. Coherence can be treated as just another library that your application depends on and uses and hence, a Coherence application can run in Kubernetes without requiring the Operator, but in this case there are a number of things that the DevOps team for an application would need to build or do manually.
JVMs that run as Coherence cluster members need to discover the other members of the cluster. This is discussed in the Coherence Well Known Addressing section of the documentation. When using the Operator the well known addressing configuration for clusters is managed automatically to allow a Coherence deployment to create its own cluster or to join with other deployments to form larger clusters.
The Operator configures the Coherence site and rack properties for cluster members based on Kubernetes Node topology labels. This allows Coherence to better distribute data across sites when a Kubernetes cluster spans availability domains.
When scaling down a Coherence cluster, care must be taken to ensure that there will be no data loss. This typically means scaling down by a single Pod at a time and waiting for the cluster to become "safe" before scaling down the next Pod. The Operator has built in functionality to do this, so scaling a Coherence cluster is as simple as scaling any other Kubernetes Deployment or StatefulSet.
Alongside safe scaling, because the Coherence CRD supports the Kubernetes scale sub-resource it is possible to configure the Kubernetes Horizontal Pod Autoscaler to scale Coherence clusters based on metrics.
Red Hat certified products are tested to meet Red Hat’s criteria and supported as defined in the Red Hat Collaborative Support Process.
Partner validated products are tested by Red Hat Partners and supported as defined in the Red Hat Third Party Component Policy.
Red Hat OpenShift 4.12, 4.14, 4.16, 4.17, 4.18, 4.19, 4.20, 4.21, 4.22
Red Hat OpenShift 4.12, 4.14, 4.16, 4.17, 4.18, 4.19, 4.20, 4.21, 4.22