Data Grid Operator 8.4 Release Notes

What’s new in 8.4.15.

Default timeout value for probes

The default timeout for probes, which was 80 seconds, has been reduced to 1 second. Reducing the default timeout helps reduce the response time for pod restart. You can also configure the timeout value according to your requirement, for more information, see Ability to customize probes.

Ability to customize probes

You can now configure the values of the Liveness, Readiness, and Startup probes used by Data Grid pods to customize the probes based on your requirements. For more information, see Configuring pod probes.

Warning when using  Cache service type

Using spec.Service.Type=Cache adversely affects the performance of RHDG. A warning is created if your deployment uses the deprecated Cache service type, spec.Service.Type=Cache. Use the DataGrid service type instead. Cache service type is planned to be removed in a future release of RHDG.

Cloud Events integration

Cloud events was available as technology preview in releases prior to Data Grid 8.4.8. The integration has been deprecated in the Data Grid 8.4.8 release and will have no effect on Data Grid releases after RHDG 8.4.x.

What’s new in 8.4.14.

Enhancements to Gossip Router

You can now configure the idle connection timeout in the Gossip Router, allowing the Gossip Router to force-close orphan TCP connection in case a Data Grid pod or a Gossip Router pod stops responding.

The Data Grid pod pings the Gossip Router at intervals defined in milliseconds. If Data Grid pod does not receive any message from the Gossip Router during the defined timeout period, Data Grid considers the connection orphan. The Gossip Router pod closes the connection if it does not receive a message or a ping from the Data Grid pod during the timeout period.

What’s new in 8.4.8.

Improved monitoring with Cryostat and JFR recordings

Data Grid now provides integration with Cryostat, that lets you monitor your Data Grid clusters that run on OpenShift using the JDK Flight Recorder (JFR). You can store and analyze your recordings using the integrated tools provided by Cryostat or export the recordings to an external monitoring application.

For more information, see Setting up JFR recordings with Cryostat.

ServiceMonitor target labels

Data Grid Operator now lets you configure target labels for the ServiceMonitor. Use the Service labels to filter and aggregate the metrics collected from the monitored endpoints.

For more information see Data Grid Operator Guide Configuring Service Monitor Target Labels.

Enhanced cross-site replication and Gossip Router configuration

Several enhancements has been made to improve experience with Data Grid cross-site replication. With Data Grid Operator, you can configure the following:

For more information, see Allocating CPU and memory for Gossip router pod.

Scheduling for Data Grid pods

You can now assign priority to the Data Grid pods to ensure that important workflows are scheduled first.

Use the spec.scheduling field, to assign priority to Data Grid pods.

kind: Infinispan
...
spec:
  scheduling:
    affinity:
      ...
    priorityClassName: "high-priority"
    ...

kind: Infinispan
...
spec:
  scheduling:
    affinity:
      ...
    priorityClassName: "high-priority"
    ...

What’s new in 8.4.5.

Allocate CPU and memory to ConfigListener

You can allocate memory and CPU resources to ConfigListener. Although ConfigListener consumes minimal resources by default, setting limits might be required for some Data Grid deployments.

The cpu and memory fields have values in the format of <limit>:<requests>.

spec:
  configListener:
    enabled:  true
    cpu: "2000m:1000m"
    memory: "2Gi:1Gi"

spec:
  configListener:
    enabled:  true
    cpu: "2000m:1000m"
    memory: "2Gi:1Gi"

What’s new in 8.4.2.

Improved security for storing sensitive strings

Data Grid Operator lets you securely define and store custom Data Grid Server configuration. To protect sensitive text strings, such as passwords, add the entries in a credential store rather than directly in the Data Grid Server configuration.

For more information see Data Grid Operator Guide Securing custom Data Grid configuration.

Configuration enhancements to ConfigListener log level

Data Grid Operator now lets you modify the log level of the ConfigListener pod. The default log level is info. You can change the log level to debug or error, if needed.

You can configure the log level of ConfigListener in your Infinispan CR as follows:

spec:
  configListener:
    enabled: true
    logging:
      level: info

spec:
  configListener:
    enabled: true
    logging:
      level: info

Strategies to update Cache CR

Data Grid Operator lets you control how the Cache CR controller handles updates to the cache configuration in the spec.template field.

Define the Cache CR update strategy as follows:

spec:
  updates:
    strategy: retain

spec:
  updates:
    strategy: retain

What’s new in 8.4 GA.

Multi-operand support

You can have a single Data Grid Operator installation that supports multiple versions of Data Grid.

Use the spec.version field in your Infinispan CR to upgrade between supported versions.

Data Grid Operator version 8.4 supports the following Data Grid versions:

For more information on upgrading Data Grid clusters see Upgrading Data Grid clusters in the Data Grid Operator Guide.

Updated OpenShift bundle for Data Grid Operator deployments

The OpenShift bundle for Data Grid Operator deployments includes images designed for 64-bit ARM architecture.

Option to disable Gossip router

Data Grid Operator starts a Gossip router on each site, but you only need a single Gossip router to manage traffic between the Data Grid cluster members.

For more information see Disabling local Gossip router and service in the Data Grid Operator Guide.

Federal Information Processing Standards (FIPS) compatibility

From now you can run Data Grid instance on a FIPS-enabled OpenShift cluster without changing your configuration. Data Grid Operator 8.4 detects that it’s running in a FIPS-enabled environment and it automatically enables FIPS mode for your Infinispan CR.

When you upgrade Data Grid Operator from version 8.3.7 to version 8.4 the -Dcom.redhat.fips=false field is removed from the Infinispan CR and FIPS mode is no longer disabled.

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

This release does not include any known issues that affect Data Grid clusters that you manage with Data Grid Operator. For complete details about Data Grid, see the Data Grid 8.4 release notes.

Data Grid Operator 8.4.14 includes the following notable fixes:

Data Grid Operator 8.4.12 includes the following notable fixes:

Data Grid Operator 8.4.11 includes the following notable fixes:

Data Grid Operator 8.4.9 includes the following notable fixes:

Data Grid Operator 8.4.8 includes the following notable fixes:

Data Grid Operator 8.4.6 includes the following notable fixes:

Data Grid Operator 8.4.5 includes the following notable fixes:

Data Grid Operator 8.4.2 includes the following notable fixes:

Data Grid Operator 8.4.0 includes the following notable fixes:

Data Grid 8.4 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.4 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

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