You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/rn-ocp-release-notes-new-features.adoc
+59-5Lines changed: 59 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -252,13 +252,67 @@ For more information, see xref:../scalability_and_performance/cnf-provisioning-l
252
252
[id="ocp-release-notes-storage_{context}"]
253
253
== Storage
254
254
255
-
////
256
-
Instructions: Add entries in the following format:
255
+
Volume Attributes Classes is generally available::
256
+
+
257
+
Volume Attributes Classes provide a way for administrators to describe "classes" of storage they offer. Different classes might correspond to different quality-of-service levels. Volume Attributes Classes was introduced in {product-title} 4.19, and is now generally available in 4.21.
258
+
+
259
+
Volume Attributes Classes is available only with AWS Elastic Block Storage (EBS) and Google Cloud Platform (GCP) persistent disk (PD) Container Storage Interface (CSI).
260
+
+
261
+
You can apply a Volume Attributes Classes to a persistent volume claim (PVC). If a new Volume Attributes Class becomes available in the cluster, you can update the PVC with the new Volume Attributes Classes if needed.
262
+
+
263
+
Volume Attributes Classes have parameters that describe volumes belonging to them. If a parameter is omitted, the default is used at volume provisioning. If a user applies the PVC with a different Volume Attributes Class with omitted parameters, the default value of the parameters might be used depending on the CSI driver implementation. For more information, see the related CSI driver documentation.
264
+
+
265
+
For more information, see xref:../storage/understanding-persistent-storage.adoc#storage-persistent-storage-pvc-volumeattributesclass_understanding-persistent-storage[Volume Attributes Classes].
257
266
258
-
Item description::
267
+
Azure File CSI supporting snapshots feature is generally available::
259
268
+
260
-
Detailed information.
261
-
////
269
+
A snapshot represents the state of the storage volume in a cluster at a particular point in time. Volume snapshots can be used to provision a new volume.
270
+
+
271
+
{product-title} 4.17 introduced volume snapshot support for the Microsoft Azure File Container Storage Interface (CSI) Driver Operator as a Technology Preview feature. In 4.21, this feature is generally available. Also, Azure File snapshots now supports Network File System (NFS) in addition to Server Message Block (SMB).
272
+
+
273
+
For more information, see xref:../storage/container_storage_interface/persistent-storage-csi.adoc#csi-drivers-supported_persistent-storage-csi[CSI drivers supported by OpenShift Container Platform] and xref:../storage/container_storage_interface/persistent-storage-csi-snapshots.adoc[CSI volume snapshots].
274
+
275
+
Azure File CSI supporting volume cloning feature is generally available::
276
+
+
277
+
Volume cloning duplicates an existing persistent volume (PV) to help protect against data loss in {product-title}. You can also use a volume clone just as you would use any standard volume.
278
+
+
279
+
{product-title} 4.16 introduced volume cloning for the Microsoft Azure File Container Storage Interface (CSI) Driver Operator as a Technology Preview feature. In 4.21, this feature is generally available. Also, Azure File cloning now supports Network File System (NFS) in addition to Server Message Block (SMB).
280
+
+
281
+
{product-title} 4.21 also introduces support for Network File System (NFS) for Azure File cloning.
282
+
+
283
+
For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-azure-file.adoc[Azure File CSI Driver Operator] and xref:../storage/container_storage_interface/persistent-storage-csi-cloning.adoc[CSI volume cloning].
284
+
285
+
oVirt CSI Driver Operator is removed from {product-title} 4.21::
286
+
+
287
+
Red Hat Virtualization (RHV) as a host platform for {product-title} was deprecated in version 4.14 and is no longer supported. In {product-title} 4.21, the oVirt CSI Driver Operator is removed.
288
+
289
+
CIFS/SMB CSI Driver Operator supports IBM Power::
290
+
+
291
+
In {product-title} 4.21, the CIFS/SMB CSI Driver Operator supports IBM Power (ppc64le).
292
+
+
293
+
For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-smb-cifs.adoc[CIFS/SMB CSI Driver Operator].
294
+
295
+
Introduction of new field to track the recovery status from resize failure::
296
+
+
297
+
{product-title} 4.19 introduced resizing recovery that stops the expansion controller from indefinitely attempting to expand a volume to an unsupported size request. This new feature allows you to recover and provide another smaller resize value for the persistent volume claim (PVC). The new value must be larger than the original volume size.
298
+
+
299
+
The problem in allowing users to reduce size is that a malicious user can use this feature to abuse the quota system. They can do so by rapidly expanding, and then shrinking the PVC.
300
+
+
301
+
{product-title} 4.21 introduces the `pvc.Status.AllocatedResourceStatus` field, which shows the recovery status of resize failure operations. If a user reduces the size of their PVCs, this new field allows resource quota to be tracked accurately.
302
+
+
303
+
For more information about resizing volumes, see xref:../storage/expanding-persistent-volumes.adoc[Expanding persistent volumes].
304
+
+
305
+
For more information about recovering when resizing volumes, see xref:../storage/expanding-persistent-volumes.adoc#expanding-recovering-from-failure_expanding-persistent-volumes[Recovering from failure when expanding volumes].
This feature allows for dynamically updating the maximum number of storage volumes a node can handle. Without this feature, volume limits are essentially immutable when a node first joins the cluster. If the environment changes—for example, if you attach a new network interface (ENI) that shares a hardware "slot" with your storage—{product-title} does not recognize it has fewer slots available for disks, leading to pods becoming stuck.
310
+
+
311
+
This feature is only supported on AWS Elastic Block Storage (EBS).
312
+
+
313
+
Mutable CSI node allocatable property is supported in {product-title} 4.21 as a Technical Preview feature. To enable this feature, you need to enable Feature Gates.
314
+
+
315
+
For more information about enabling Technical Preview features, see xref:../nodes/clusters/nodes-cluster-enabling-features.adoc[Feature Gates].
0 commit comments