Red Hat SummitDieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 2. New features
This section describes new features introduced in Red Hat OpenShift Data Foundation 4.21.
2.1. Disaster Recovery
2.1.1. Multi-volume consistency for Disaster Recovery
Multi-volume consistency group support is now fully supported again for both, RBD and CephFS volumes. Consistency groups is used by default for all newly protected applications. Already protected non-CG applications on an upgraded cluster applications should be unprotected and protected again to migrate to consistency groups.
For more information, see Enabling consistency groups for disaster recovery using CephFS volumes.
2.1.2. Support for CephFS Volumes Using Non‑Default StorageClasses
OpenShift Data Foundation DR solution supports data replication for CephFS volumes that use multiple or non‑default StorageClasses, such as replica‑2 file storage. This enhancement enables disaster recovery for workloads backed by customized CephFS configurations, including cases where different pools or secrets require separate StorageClass, VolumeSnapshotClass, and VolumeReplicationClass resources.
2.1.3. Enhanced Disaster Recovery Capabilities in the RHACM KubeVirt UI
Disaster Recovery Integration for Virtual Machines
The Red Hat Advanced Cluster Management for Kubernetes (RHACM) KubeVirt UI now integrates OpenShift Data Foundation disaster recovery, allowing users to view VM protection status and initiate DR protection directly from the VM view. This capability is available for both GitOps‑managed and discovered VMs, with disabled actions providing guidance when prerequisites are not met.
Improved Visibility for Failover and Relocate Operations
The RHACM UI now surfaces detailed, step‑by‑step progression for Disaster Recovery failover and relocate workflows using progression data from Ramen. Enhanced modals show each operation phase, status indicators, and any associated errors, improving transparency, troubleshooting speed, and overall observability of DR processes.
2.2. Networking
2.2.1. IPv6 Support for Multus Networks
Multus supports IPv6, allowing customers to configure their Multus networks as IPv4‑only or IPv6‑only. This enhancement improves network flexibility and supports modern dual‑stack deployment needs. Both Multus networks must use the same IP family when multiple networks are configured.
2.2.2. IPv6 Support for External Mode
OpenShift Data Foundation clusters deployed in external mode now support single‑stack IPv6, in addition to IPv4, enabling deployments in environments where IPv6 is required with limited IPv4 availability. This enhancement aligns OpenShift Data Foundation external mode with OpenShift’s IPv6 capabilities and expands deployment flexibility for customers operating in IPv6‑centric infrastructures.
2.3. ARM architecture support in OpenShift Data Foundation
OpenShift Data Foundation components can now run on ARM-based clusters.
2.4. Configurable MON timeout for improved node live migration stability
OpenShift Data Foundation now supports configuring the Ceph MON timeout through a YAML update, enabling clusters to accommodate longer node live‑migration times in environments such as bare metal with OpenShift Virtualization. This enhancement helps prevent unnecessary MON failovers during upgrades or maintenance operations where live migrations may exceed the previous fixed 10‑minute threshold, improving cluster stability and operational reliability.
For more information, see Configuring Ceph monitor failover timeout.
2.5. Health Overview and scoring
A new Health Overview provides a single, summarized health score based on infrastructure checks that impact OpenShift Data Foundation performance and stability. The score starts at 100% and is reduced based on detected issues, with severity‑based deductions for minor, medium, and critical conditions. Automated checks include node‑to‑node latency, MTU validation, disk and NIC utilization, and pod restarts observed within the last 24 hours. The UI displays the overall score, lists failed checks, raises alerts when thresholds are exceeded, and allows users to acknowledge issues to exclude them from the score calculation.
For more information, see Viewing OpenShift Data Foundation infrastructure health.
2.6. Automated detection of stale CephFS subvolumes
A new automated scan helps identify stale CephFS subvolumes that may cause OpenShift Data Foundation clusters to appear full even after volumes are deleted. When stale subvolumes are detected, the system now generates alerts and provides runbook guidance, reducing the need for manual troubleshooting and lowering overall maintenance effort for customers.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}