Este conteúdo não está disponível no idioma selecionado.

Chapter 3. Enhancements


This section describes the major enhancements introduced in Red Hat OpenShift Data foundation 4.14.

3.1. Support for higher disk capacities and disk quantities

Previously, for local storage deployments, Red Hat recommended 9 devices or less per node and disks size of 4 TiB or less. With this update, the recommended devices per node is now 12 or less, and disks size is 16 TiB or less.

Note

Confirm the estimated recovery time using the OpenShift Data Foundation Recovery Calculator. It is recommended that the recovery time for host failure to be under 2 hours.

3.2. Faster RWO recovery in case of node failures

Previously, it took a long time for ReadWriterOnce (RWO) volumes to recover in case of node failures. With this update, the issue has been fixed.

For the cluster to automatically address node failures and recover RWO volumes faster, manually add one of the following taints to the node:

  • node.kubernetes.io/out-of-service=nodeshutdown:NoExecute
  • node.kubernetes.io/out-of-service=nodeshutdown:NoSchedule

3.3. Automatic space reclaiming for RBD persistent volume claims PVCs

Red Hat OpenShift Data Foundation version 4.14 introduces automatic space reclaiming for RBD persistent volume claims PVCs that are in the namespace that begins with openshift-. This means administrators no longer have to manually reclaim space for the RBD PVCs in the namespace that starts with openshift- prefix.

3.4. Automation of annotating encrypted RBD storage classes

Annotation is automatically set when the OpenShift console creates a RADOS block device (RBD) storage class with encryption enabled. This enables customer data integration (CDI) to use host-assisted cloning instead of the default smart cloning.

3.5. LSOs LocalVolumeSet and LocalVolumeDiscovery CRs now support mpath device types

With this release, disk and mpath device types are available for LocalVolumeSet and LocalVolumeDiscovery CRs.

OpenShift Data Foundation deployments using OpenShift Virtualization platform will now have a new StorageClass automatically created and it can be set as a default storage class for OpenShift Virtualization. This new StorageClass is optimized for OpenShift virtualization using a specific preset of the underlying storage.

3.7. Collect rbd status details for all images

When troubleshooting certain RBD related problems, the status of the RBD-images is an important information. With this release, for the OpenShift Data Foundation internal mode deployment, odf-must-gather includes the rbd status details, making it faster to troubleshoot RBD related problems.

3.8. Change in default permission and FSGroupPolicy

Permissions of newly created volumes now defaults to a more secure 755 instead of 777. FSGroupPolicy is now set to File (instead of ReadWriteOnceWithFSType in ODF 4.11) to allow application access to volumes based on FSGroup. This involves Kubernetes using fsGroup to change permissions and ownership of the volume to match user requested fsGroup in the pod’s SecurityPolicy.

Note

Existing volumes with a huge number of files may take a long time to mount since changing permissions and ownership takes a lot of time.

For more information, see this knowledgebase solution.

Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat