Chapter 2. New features

Red Hat OpenShift Data Foundation Disaster Recovery (DR) provides crash consistent multi-volume consistency groups for Regional-DR to be used by applications that are deployed over multiple volumes. This is especially important for VirtualMachines that sometimes have multiple disks attached to it. For more information, see Multi-volume consistency for disaster recovery.

Health status for the Red Hat Advanced Cluster Management (RHACM) managed applications is displayed on the application list page which helps to monitor the health status of the disaster recovery. For more information, see Viewing health status of ApplicationSet-based and Subscription-based applications.

The capabilities of DR recipes are enhanced to support more applications to provide automated disaster recovery for CephFS based applications that are deployed with imperative models.

Red Hat Advanced Cluster Management (RHACM) managed clusters allow replication of data that is using non-default storage classes that are managed by OpenShift Data Foundation. This is important for customers leveraging replica 2 storage classes. This is available for Regional DR using Ceph RBD block volumes.

Starting with this release, Multicloud Object Gateway (MCG) runs with high availability for metadata databases (DB). This helps to avoid a single point of failure for MCG DB, which puts data at risk in case of a node failure.

Cross-origin resource sharing (CORS) is supported for Multicloud object Gateway buckets for increased coverage and compatibility with AWS::S3. CORS defines a way for client web applications that are loaded in one domain to interact with resources in a different domain.

For more information, see Creating Cross Origin Resource Sharing (CORS) rule and Editing Cross Origin Resource Sharing (CORS) rule.

An overriding policy option can be created to block public access to the buckets. This increases the compatibility with Amazon S3. This option enables administrators and bucket owners to limit public access to their resources that are enforced regardless of how the resources are created.

For more information, see Configuring or modifying the PublicAccessBlock configuration for S3 bucket.

Additional expiration rules are supported to avoid size inflation and manual operations to identify and delete the undesired objects. These rules help the bucket owner to better control the usage of storage and fine-tune the objects that they want to keep or expire. The following rules are supported and these rules are available in the user interface in object browser:

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