Data Grid Operator 8.5 Release Notes

What is new in 8.5.11.

Configurable termination grace period for Infinispan pods

You can configure the termination grace period for Infinispan pods through the Infinispan Custom Resource (CR). Previously, the Operator always used a default value of 30 seconds. This enhancement provides flexibility for clusters with large caches that require more time to persist data during shutdown.

Limitations on deploying multiple Data Grid Operator versions

Due to the Operator Lifecycle Manager (OLM) and Custom Resource Definitions (CRDs) being deployed cluster-wide, you cannot deploy different versions of the Data Grid Operator on the same cluster. To avoid issues, deploy the Operator cluster-wide and use the spec.version field in your Data Grid server custom resources to control server version upgrades.

For more information, see Data Grid Operator 8.4.x and 8.5.x spec.version feature

What is new in 8.5.8.

Graceful shutdown restricted for degraded cluster state

Graceful shutdown is now blocked if any cache is not in a HEALTHY state or if the cluster view has fewer members than the configured number of replicas. This prevents unintended scale-down operations during split-brain or rebalancing conditions that could result in data loss.

What is new in 8.5.6.

The 8.5.6 release includes only bug fixes. For more information, see Fixed in Data Grid Operator 8.5.6.

What is new in 8.5.4.

Setting CPU and memory limits in Batch CR

With this update, you can limit the number of CPU requests and memory allocation in a Batch Custom Resource (CR). For example:

apiVersion: infinispan.org/v2alpha1
kind: Batch
metadata:
  name: exampleBatch
spec:
  cluster: infinispan
  configMap: mybatch-config-map
  container:
    cpu: "2000m:1000m" 
    memory: "2Gi:1Gi"  

apiVersion: infinispan.org/v2alpha1
kind: Batch
metadata:
  name: exampleBatch
spec:
  cluster: infinispan
  configMap: mybatch-config-map
  container:
    cpu: "2000m:1000m" 

    memory: "2Gi:1Gi"  

Customizing log display in log traces

You can now customize the log display for Data Grid log traces by defining the spec.logging.pattern field in your Infinispan CR.

If you do not define a custom pattern, the default format is the following:

%d{HH:mm:ss,SSS} %-5p (%t) [%c] %m%throwable%n

%d{HH:mm:ss,SSS} %-5p (%t) [%c] %m%throwable%n

For more information, see Adjusting log pattern.

Support for auto scaling with HorizontalPodAutoscaler

StatefulSets or Deployments can now be automatically scaled up or down based on specified metrics by defining a HorizontalPodAutoscaler resource in the same namespace as the Infinispan CR.

For more information, see Auto Scaling.

What’s new in 8.5.3.

Automatic reloading of SSL/TLS certificates

Starting with Data Grid 8.5.1, Data Grid monitors keystore files for changes and automatically reloads them, without requiring a server or client restart, when certificates are renewed.

Therefore, with Data Grid Operator 8.5.3, StatefulSet rolling update is not triggered on key or truststore update in a server when managing Data Grid 8.5.1 Operands because it is not required.

What’s new in 8.5.0.

Ability to configure InitContainer resource

You can now configure the InitContainer resource. Previously, if a LimitRange was in effect for the deployment namespace, then the InitContainer would be restricted to these resource values causing issues such as OutOfMemoryError. You can configure InitContainer resource configuration in the Data Grid CR as follows:

spec:
  dependencies:
    initContainer:
      cpu: "2000m:1000m"
      memory: "2Gi:1Gi"

spec:
  dependencies:
    initContainer:
      cpu: "2000m:1000m"
      memory: "2Gi:1Gi"

Ability to define Batch resource CPU and memory request/limits

You can now define CPU and memory request/limits for Batch Job created by the Operator. You can define the resource request/limits in the Batch CR as follows:

apiVersion: infinispan.org/v2alpha1
kind: Batch
metadata:
  name: mybatch
spec:
  cluster: infinispan
  configMap: mybatch-config-map
  container:
    cpu: "2000m:1000m"
    memory: "2Gi:1Gi"

apiVersion: infinispan.org/v2alpha1
kind: Batch
metadata:
  name: mybatch
spec:
  cluster: infinispan
  configMap: mybatch-config-map
  container:
    cpu: "2000m:1000m"
    memory: "2Gi:1Gi"

TLSv1.3 encryption for cross-site encryption

The default encryption protocol for cross-site is now TLSv1.3 instead of TLSv1.2.

Ability to define TopologyPodConstraints and Tolerations in StatefulSet

You can now configure more advanced high availability configurations by defining TopologyPodConstraints and Tolerations in spec.statefulSet.

kind: Infinispan
...
spec:
  scheduling:
    affinity:
      ...
    tolerations:
      ...
    topologySpreadConstraints:
      ...

kind: Infinispan
...
spec:
  scheduling:
    affinity:
      ...
    tolerations:
      ...
    topologySpreadConstraints:
      ...

Cache service type removed

RHDG 8.5 removes the Cache service type cache. Instead, use the DataGrid service type to automate complex operations such as cluster upgrades and data migration.

Cloud events removed

RHDG 8.5 removes cloud events integration.

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.5 release notes.

Data Grid Operator 8.5.8 includes the following notable fixes:

Data Grid Operator 8.5.6 includes the following notable fixes:

Data Grid Operator 8.5.4 includes the following notable fixes:

Data Grid Operator 8.5.3 includes the following notable fixes:

Data Grid Operator 8.5.0 includes the following notable fixes:

Data Grid 8.5 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.5 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