Chapter 2. New Features

The regional disaster recovery (Regional-DR) is generally available for block and file applications. Improvements made to Regional-DR in this release includes the following fixes among other fixes:

Regional-DR is supported only with OpenShift Data Foundation 4.14 and Red Hat Advanced Cluster Management for Kubernetes 2.9 combinations. Support for existing pre OpenShift Data Foundation 4.14 deployments upgrade to Regional-DR is currently in progress and expected to be available in the near future.

For more information, see the Regional-DR section in the Planning guide and Regional-DR solution for OpenShift Data Foundation.

Red Hat OpenShift Data Foundation version 4.14 introduces IPv6 auto detection and configuration. OpenShift clusters using IPv6 or dual-stack are automatically configured in OpenShift Data Foundation accordingly.

For more information about IPv6, see IPv6 support.

Red Hat OpenShift Data Foundation version 4.14 now supports the Metro-DR and Regional-DR solution on IBM Z and IBM Power platforms. With the enablement of disaster recovery, business continuity is maintained when any disaster hits a geographical location or a data center. Red Hat Ceph Storage (RHCS) deployment is supported only on x86 architecture on IBM Z and IBM Power.

For more information, see Configuring OpenShift Data Foundation Disaster Recovery for OpenShift Workloads.

With this release, Multicloud Object Gateway (MCG) bucket replication is scalable. This helps to replicate data faster on a larger scale. The bucket replication uses the event logs of the Amazon Web Services (AWS) and Microsoft Azure cloud environments to optimize the replication.

For more information, see Enabling log based bucket replication in AWS and Enabling log based bucket replication in Microsoft Azure.

With this release, two new autoscalers based on HPAV2 (default) and KEDA are available. These autoscalers provide support for MCG endpoint autoscaling using Prometheus metrics.

KEDA is not supported on IBM Power as KEDA images are not available for Power architecture.

Deletion of expired objects is a simplified way that enables handling of unused data. This reduces the storage costs due to accumulated data objects. The unused data is deleted after expiration. Data expiration is a part of Amazon Web Services (AWS) lifecycle management and sets an expiration date for automatic deletion. The minimal time resolution of the lifecycle expiration is one day.

For more information, see Lifecyle bucket configuration in Multicloud Object Gateway.

With this release, you can deploy the Multicloud Object Gateway component using the local storage devices on IBM Z. Deploying only the Multicloud Object Gateway component with the OpenShift Data Foundation provides the flexibility in deployment and helps to reduce the resource consumption.

With this release, multi-network plug-in, Multus, is generally available. OpenShift Data Foundation supports the ability to use Multus on bare metal infrastructures to improve security and performance by isolating the different types of network traffic. By using Multus, one or more network interfaces on hosts can be reserved for exclusive use of OpenShift Data Foundation.

Deployment of OpenShift Data Foundation is now supported on Google Cloud. For more information see, the Deploying OpenShift Data Foundation using Google Cloud guide.