Data Grid Operator 8.6 Release Notes

Red Hat recommends using the latest available Data Grid Operator version to ensure access to the most recent features, security updates, and compatibility fixes.

Starting with Data Grid Operator 8.4.x (channel 8.4.x), a single Data Grid Operator version can manage multiple Data Grid cluster versions. This capability is provided through the spec.version feature, which enables you to select the Data Grid container image version for each cluster.

When deploying Data Grid with the Data Grid Operator, ensure the following compatibility considerations:

For detailed compatibility and lifecycle information, refer to the following documentation:

What’s new in 8.6.0.

Data Grid Operator base image migration to Konflux-built UBI

In Red Hat Data Grid 8.6.0, the Data Grid Operator container base image has been migrated from registry.redhat.io/rhel8-osbs/osbs-ubi8-micro to registry.redhat.io/ubi9/ubi-micro.

Rolling upgrade strategy for zero-downtime upgrades

The Data Grid Operator introduces a rolling upgrade strategy to enable zero-downtime upgrades within 8.6.x clusters.

When spec.upgrades.type is set to InPlaceRolling, the Data Grid Operator upgrades nodes one at a time using a StatefulSet rolling update while the cluster remains available.

For upgrades that cannot use rolling updates, use the Shutdown strategy.

apiVersion: infinispan.org/v1
kind: Infinispan
metadata:
  name: infinispan
spec:
  version: 8.6.1-1
  upgrades:
    type: InPlaceRolling

Grafana Operator version support

Grafana Operator V4 is no longer supported, and Operator automation does not work with Grafana Operator V5.

The following table provides detailed version information for Data Grid Operator.

This section describes issues that affect Data Grid clusters that you manage with Data Grid Operator. For complete details about Data Grid, see the Data Grid 8.6 release notes.

Description: On FIPS-enabled OpenShift clusters, the Data Grid Operator fails to retrieve cluster status and cannot set the WellFormed condition. The issue occurs because scram-sha-256 is configured as a SASL mechanism for the Operator connector, and the underlying OpenJDK disables this algorithm. This results in broken communication between the Data Grid Operator and servers.

Workaround: There is no workaround for this issue.

Data Grid 8.6 includes two container images, the Data Grid Operator image and Data Grid Server image.

Data Grid images are hosted on the Red Hat Container Registry, where you can find health indexes for the images along with information about each tagged version.

Custom Data Grid Deployments

Red Hat does not support customization of any 8.6 images from the Red Hat Container Registry through the Source-to-Image (S2I) process or ConfigMap API.

As a result it is not possible to use custom:

Using embedded Data Grid caches in applications running on OpenShift, which was referred to as Library Mode in previous releases, is intended for specific uses only:

Red Hat supports only DNS_PING as the cluster discovery mechanism.

DNS_PING exposes a port named ping that Data Grid nodes use to perform discovery and join clusters. TCP is the only supported protocol for the ping port, as in the following example for a pod on OpenShift:

spec:
  ...
  ports:
    - name: ping
      port: 8888
      protocol: TCP
      targetPort: 8888