Chapter 3. Enhancements

Multicloud Object Gateway (MCG) object browser is enhanced to provide additional browsing features, such as setting expiration policy, setting bucket policy, sorting the buckets by name, modified time, size, and versioning management.

For more information, see Creating and managing buckets using MCG object browser.

Previously, MCG backing stores configured with multiple volumes and a 'spread' policy did not evenly distribute preexisting data across volumes. As a result, NooBaa continued writing only to volumes with available space, leading to uneven utilization and repeated “nearly full” PVC alerts.

With this release, MCG automatically balances data evenly across all volumes in a backing store configured with a 'spread' policy, so that storage efficiency is maximized without needing to manually redistribute data. This allows scaling storage easily and maintaining consistent and efficient storage utilization.

Previously, MCG always set the same label for a PV-Pool backing store for deployments with multiple such backing stores

With this release, modifying the matchLabel of topologySpreadConstraints for MCG’s backing store pods is allowed as it is needed to differentiate between the pods using different labels.

Placement group (PG) counts per OSD across OpenShift Data Foundation Ceph pools are increased to a default of 200 PGs per OSD. Previously, the default was 100. This leads to an increased PG count across ODF pools. This helps to achieve better performance by increasing parallelism during I/O operations and improves the balancing of capacity across underlying storage devices.

Previously, there was no validation to check whether the mode of an original volume (filesystem or raw block), whose snapshot was taken, matched the mode of a newly created volume. This presented a security gap that could allow malicious users to potentially exploit an as-yet-unknown vulnerability in the host operating system.

However, some users have a legitimate need to perform such conversions. This feature allows cluster administrators to provide these rights (ability to perform update or patch operations on VolumeSnapshotContents objects) only to trusted users or applications, such as backup vendors.

To convert a volume mode, an authorized user needs to change snapshot.storage.kubernetes.io/allow-volume-mode-change: "true" for VolumeSnapshotContent of the snapshot source.

The user interface for the creation of Local Volume Set and Local Volume Discovery for the local storage operator is updated in the OpenShift console.

For more information, see Persistent storage using local volumes.