Data Grid Operator 8.1 Release Notes
Data Grid Operator 8.1
Abstract
Red Hat Data Grid
Data Grid is a high-performance, distributed in-memory data store.
- Schemaless data structure
- Flexibility to store different objects as key-value pairs.
- Grid-based data storage
- Designed to distribute and replicate data across clusters.
- Elastic scaling
- Dynamically adjust the number of nodes to meet demand without service disruption.
- Data interoperability
- Store, retrieve, and query data in the grid from different endpoints.
Data Grid documentation
Documentation for Data Grid is available on the Red Hat customer portal.
Data Grid downloads
Access the Data Grid Software Downloads on the Red Hat customer portal.
You must have a Red Hat account to access and download Data Grid software.
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Upgrade to the latest Data Grid version
Red Hat recommends you upgrade any deployments from 8.1.x to the latest Data Grid 8 version as soon as possible. The Data Grid team regularly patch security vulnerabilities and actively fix issues on the latest version of the software.
1.1. Apache Log4j security vulnerabilities
Data Grid includes Apache Log4j components in:
- Data Grid Server distribution
- Data Grid Server container image for Red Hat OpenShift
Data Grid 8.2.2 fixes CVE-2021-44228 which is a critical security vulnerability. Data Grid 8.2.3 fixes several Log4j CVEs of moderate severity. For more information, see the Data Grid 8.2 release notes or the Data Grid Operator 8.2 release notes. You can find the latest Data Grid documentation at Red Hat Data Grid Product Documentation.
Data Grid Operator version 8.2.7 corresponds to Data Grid 8.2.2.
If you cannot upgrade your Data Grid deployment, you must follow the steps to mitigate the critical vulnerability as outlined in the RHSB-2021-009 Log4Shell - Remote Code Execution security bulletin.
Chapter 2. Data Grid Operator 8.1
Learn about new features and get version details for Data Grid Operator 8.1.
2.1. Version Details
The following table provides detailed version information for Data Grid Operator.
Data Grid Operator versions do not always directly correspond to Data Grid versions because the release schedule is more frequent.
| Data Grid Operator version | Data Grid version | Features |
|---|---|---|
| 8.1.6 | 8.1.1 | * Bug fixes.
* Configurable * Documentation improvements for creating routes, Hot Rod client configuration, and cache creation. * Fixes security vulnerabilities. |
| 8.1.5 | 8.1.1 | * Support for custom labels. * Metering labels for Red Hat subscriptions. * Fixes security vulnerabilities. |
| 8.1.4 | 8.1.1 | * Anti-affinity settings. * Ability to disable encryption. * Multiple namespace installation. |
| 8.1.3 | 8.1.0 | Fixes security vulnerabilities. |
| 8.1.2 | 8.1.0 | Fixes security vulnerabilities. |
| 8.1.1 | 8.1.0 | Fixes security vulnerabilities. |
| 8.1.0 | 8.1.0 | * Cross-site replication. * Automatic scaling. * Ability to expose services via routes. * Automatic encryption with the OpenShift service CA.
* * Configurable number of owners for Cache service nodes. |
2.2. Data Grid Operator 8.1 GA
Find out what’s new with Data Grid Operator for Data Grid 8.1.
2.2.1. Cross-Site Replication
Data Grid Operator improves setup and management of cross-site replication capabilities for Data Grid clusters running on OpenShift.
2.2.2. Expose Services via Routes
Data Grid Operator updates the spec.expose resource so you can create OpenShift Routes with passthrough encryption to make Data Grid clusters available on the network.
2.2.3. Automatic Scaling
Data Grid Operator can automatically scale the default cache on Cache service nodes up or down based on memory usage.
2.2.4. Automatic Encryption with the OpenShift Service CA
By default, if the Red Hat OpenShift service CA is available, Data Grid Operator generates TLS certificates, signed by the Red Hat OpenShift service CA, to encrypt client connections.
You must use encryption if the OpenShift service CA is present.
If you are upgrading from 8.0, you should retrieve the generated tls.crt certificate and add it to a client trust store.
2.2.5. Cache Custom Resource
You can now create caches with Data Grid service nodes with the Cache CR.
Creating caches with Data Grid Operator is available as a technology preview.
Technology Preview features or capabilities are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
2.2.6. Number of Owners
Cache service nodes now use a default value of 2 for the number of owners, which replicates each entry across the cluster. You can modify the number of owners with the spec.service.replicationFactor resource in your Infinispan CR.
Chapter 3. Data Grid on OpenShift
3.1. Data Grid 8.1 Images
Data Grid 8.1 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.
Red Hat supports Data Grid 8.1 on OpenShift only through Data Grid Operator subscriptions.
Custom Data Grid Deployments
Red Hat does not support customization of any 8.1 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:
- Discovery protocols
- Encryption mechanisms (SYM_ENCRYPT or ASYM_ENCRYPT)
- Persistent datasources
Additional resources
3.2. Data Grid Library Mode on OpenShift
Embedding Data Grid in custom applications, also referred to as Library Mode, is intended for specific uses only when running on OpenShift:
- Using local or distributed caching in custom Java applications to retain full control of the cache lifecycle. Additionally, when using features that are available only with embedded Data Grid such as distributed streams.
-
Reducing network latency to improve the speed of cache operations.
The Hot Rod protocol provides near-cache capabilities that achieve equivalent performance to a standard client-server architecture.
Requirements
Embedding Data Grid in applications running on OpenShift requires you to use a discovery mechanism so Data Grid nodes can form clusters to replicate and distribute data.
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: 8888Limitations
Embedding Data Grid in applications running on OpenShift also has some specific limitations:
- Persistent cache stores are not currently supported.
- UDP is not supported with embedded Data Grid.
Custom caching services
Red Hat highly discourages embedding Data Grid to build custom caching servers to handle remote client requests. To benefit from regular, automatic updates with performance improvements and fix security issues, you should create Data Grid clusters with the Data Grid Operator instead.
Reference
