Chapter 3. Enhancements

A new flag has been added to enable forceful deployment of the storage cluster. This helps redeployment with automation.

For more information, see the knowledgebase article Install Red Hat OpenShift Data Foundation 4.X in internal-attached mode using command line interface..

With this release, annotations required for encrypted StorageClasses are now automatically added when Key Management Services (KMS) are missing. This streamlines key rotation and improves security configuration.

Pool level alerts for near full and full status of the pool are now available with actionable messages.

For more information, see Resolving cluster alerts.

An alert is triggered when CSI clones or snapshots approach the soft limit of 200. This notification recommends switching to volume snapshot cloning for better performance, helping to avoid delays caused by excessive clone operations.

This release introduces improvements to the DR uninstall workflow, streamlining the removal of resources created during various stages of DR deployment. Previously, uninstalling DR components required manual cleanup across multiple layers. With this enhancement, the uninstall process is more intuitive and automated.

Resource requirements for OpenShift Data Foundation components are now merged with default values instead of being fully replaced. If a user specifies only one resource type such as memory, OpenShift Data Foundation will automatically apply default values for the other type, like CPU. Previously, partial specifications caused missing fields to be dropped, leading to components running without complete resource settings and resulting in unpredictable performance. This enhancement ensures safer and more balanced configurations with minimal user input.

(DFBUGS-426)

Placement configuration for components has been improved to support selective merging. Previously, specifying any placement section such as, Tolerations would override the entire default placement, leaving other sections like Node Affinity or Topology Spread Constraints empty. This caused incomplete or suboptimal placement configurations.

With this enhancement, OpenShift Data Foundation now merges user-defined placement values with the default configuration. Users can specify only the sections they want to customize, while defaults for other placement types are preserved, ensuring consistent and expected placement behavior for components.

(DFBUGS-3835)

VolSync DataMover pods could not access data when using custom Security Context Constraints (SCCs), leading to sync failures in clusters with custom configurations. The DRPC spec now includes a VolSyncSpec field that allows users to configure the following:

These configurations are propagated to the VolumeReplicationGroup (VRG), ensuring VolSync components inherit the required privileges for successful operation.

(DFBUGS-3713)

Users can now configure memory and CPU for kube-rbac-proxy pods through the custom resource (CR). This enhancement addresses out-of-memory (OOM) issues encountered during ocs-metrics-exporter operations. By allowing resource adjustments, users can prevent running into these issues.

(DFBUGS-3286)