Merge pull request #93118 from lpettyjo/rel_notes_4_19

Rel Notes for Storage 4.19

Author: lpettyjo

release_notes/ocp-4-19-release-notes.adoc

@@ -889,6 +889,89 @@ With this release, the secrets store providers support using the {secrets-store-
 
 For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-secrets-store.adoc#persistent-storage-csi-secrets-store-disconnect-environment_persistent-storage-csi-secrets-store[Support for disconnected environments].
 
+[id="ocp-release-notes-storage-azure-file-cross-sub-support_{context}"]
+==== Azure File cross-subscription support is generally available
+Cross-subscription support allows you to have an {product-title} cluster in one Azure subscription and mount your Azure file share in another Azure subscription using the Azure File Container Storage Interface (CSI) driver. The subscriptions must be in the same tenant.
+
+This feature is generally available in {product-title} 4.19.
+
+For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-aws-efs.adoc#persistent-storage-csi-efs-cross-account_persistent-storage-csi-aws-efs[AWS EFS CSI cross account support].
+
+[id="ocp-release-notes-storage-vol-attributes_{context}"]
+==== Volume Attributes Classes (Technology Preview)
+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 in {product-title} 4.19 is available only with AWS Elastic Block Storage (EBS) and Google Cloud Platform (GCP) persistent disk (PD) Container Storage Interface (CSI).
+
+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.
+
+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.
+
+Volume Attributes Classes is available in {product-title} 4.19 with Technology Preview status.
+
+For more information, see xref:..//storage/understanding-persistent-storage.adoc#storage-persistent-storage-pvc-volumeattributesclass_understanding-persistent-storage[Volume Attributes Classes].
+
+[id="ocp-release-notes-storage-cli-cmd-pvc-usage_{context}"]
+==== New CLI command to show PVC usage (Technology Preview)
+{product-title} 4.19 introduces a new command to view persistent volume claim usage. This feature has Technology Preview status.
+
+For more information, see xref:../storage/understanding-persistent-storage.adoc#pvc-cli-command-usage_understanding-persistent-storage[Viewing PVC usage statistics].
+
+[id="ocp-release-notes-storage-cli-cmd-resize-recovery_{context}"]
+==== CSI volume resizing recovery is generally available
+Previously, you might expand a persistent volume claim (PVC) to a size that is not supported by the underlying storage provider. In this case, the expansion controller typically tries forever to expand the volume and keeps failing. 
+
+This new feature allows you to recover and provide another resize value for the PVC. Resizing recovery is supported as generally available in {product-title} 4.19.
+
+For more information about resizing volumes, see xref:../storage/expanding-persistent-volumes.adoc[Expanding persistent volumes].
+
+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].
+
+[id="ocp-release-notes-storage-resize-migrated-vsphere-in-tree-vols_{context}"]
+==== Support for resizing vSphere in-tree migrated volumes is generally available
+Previously, VMware vSphere persistent volumes that were migrated from in-tree to Container Storage Interface (CSI) could not be resized. With {product-title} 4.19, resizing migrated volumes is supported. This feature is generally available.
+
+For more information about resizing volumes, see xref:../storage/expanding-persistent-volumes.adoc[Expanding persistent volumes].
+
+[id="ocp-release-notes-storage-disable-vsphere_{context}"]
+==== Disabling and enabling storage on vSphere is generally available
+Cluster administrators might want to disable the VMWare vSphere Container Storage Interface (CSI) Driver as a Day 2 operation, so the vSphere CSI Driver does not interface with your vSphere setup. 
+
+This features was introduced in {product-title} 4.17 with Technology Preview status. This feature is now supported as generally available in {product-title} 4.19.
+
+For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-disable-storage-overview_persistent-storage-csi-vsphere[Disabling and enabling storage on vSphere].
+
+[id="ocp-release-notes-storage-increase-max-vols-per-node-vsphere"]
+==== Increasing the maximum number of volumes per node for vSphere (Technology Preview)
+For VMware vSphere version 7, {product-title} restricts the maximum number of volumes per node to 59.
+
+However, with {product-title} 4.19 for vSphere version 8 or later, you can increase the allowable number of volumes per node to a maximum of 255. Otherwise, the default value remains at 59.
+
+This feature has Technology Preview status.
+
+For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-increase-max-vols-per-node-overview_persistent-storage-csi-vsphere[Increasing maximum volumes per node for vSphere].
+
+[id="ocp-release-notes-storage-vsphere-migrating-cns-vols-between-datastores_{context}"]
+==== Migrating CNS volumes between datastores for vSphere is fully supported
+If you are running out of space in your current datastore, or want to move to a more performant datastore, you can migrate VMware vSphere Cloud Native Storage (CNS) volumes between datastores. This applies to both attached and detached volumes.
+
+{product-title} now fully supports migration of CNS volume using the vCenter UI. Migrated volumes should work 
+as expected and should not result in non-functional persistent volumes. CNS volumes can also be migrated while in use by pods.
+
+This feature was introduced as a Development Preview in {product-title} 4.17, but is now fully supported  in 4.19.
+
+Migrating CNS volumes between datastores requires VMware vSphere 8.0.2 or later or vSphere 7.0 Update 3o or later.
+
+For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-migrating-cns-vols-between-datastores_persistent-storage-csi-vsphere[Migrating CNS volumes between datastores for vSphere].
+
+[id="ocp-release-notes-storage-nfs-export-options-filestore"]
+==== NFS export options for Filestore storage class is generally available.
+By default, a Filestore instance grants root level read/write access to all clients that share the same Google Cloud project and virtual private cloud (VPC) network. Network File System (NFS) export options can limit this access to certain IP ranges and specific user/group IDs for the Filestore instance. When creating a storage class, you can set these options using the `nfs-export-options-on-create` parameter.
+
+NFS export options is supported as generally available in {product-title} 4.19.
+
+For more information, see xref:..//storage/container_storage_interface/persistent-storage-csi-google-cloud-file.adoc#persistent-storage-csi-gcp-filestore-nfs-export-options_persistent-storage-csi-google-cloud-file[NFS export options].
+
 [id="ocp-release-notes-web-console_{context}"]
 === Web console
 
@@ -1163,6 +1246,11 @@ In the following tables, features are marked with the following statuses:
 |====
 |Feature |4.17 |4.18 |4.19
 
+|Persistent storage using FlexVolume
+|Deprecated
+|Deprecated
+|Deprecated
+
 |AliCloud Disk CSI Driver Operator
 |Removed
 |Removed
@@ -2093,6 +2181,11 @@ In the following tables, features are marked with the following statuses:
 |Technology Preview
 |Technology Preview
 
+|Azure File cross-subscription support
+|Not Available
+|Not Available
+|General Availability
+
 |Shared Resources CSI Driver in OpenShift Builds
 |Technology Preview
 |Technology Preview
@@ -2116,6 +2209,11 @@ In the following tables, features are marked with the following statuses:
 |Disabling/enabling storage on vSphere
 |Technology Preview
 |Technology Preview
+|General Availability
+
+|Increasing max number of volumes per node for vSphere
+|Not Available
+|Not Available
 |Technology Preview
 
 |RWX/RWO SELinux Mount
@@ -2126,7 +2224,7 @@ In the following tables, features are marked with the following statuses:
 |Migrating CNS Volumes Between Datastores
 |Developer Preview
 |Developer Preview
-|Developer Preview
+|General Availability
 
 |CSI volume group snapshots
 |Not Available
@@ -2147,6 +2245,11 @@ In the following tables, features are marked with the following statuses:
 |Not Available
 |General Availability
 |General Availability
+
+|Volume Attribute Classes
+|Not Available
+|Not Available
+|Technology Preview
 |====
 
 [discrete]
@@ -2194,6 +2297,8 @@ To save the `vmcore` file, use the `crashkernel` setting to reserve 1024 MB of m
 
 [id="ocp-storage-core-4-19-known-issues_{context}"]
 
+* NFS volumes exported from VMWare vSAN Files cannot be mounted by clusters running {product-title} 4.19 due to RHEL-83435. To avoid this issue, ensure that you are running VMWare ESXi and vSAN at the latest patch versions of 8.0 P05, or later. (link:https://issues.redhat.com/browse/OCPBUGS-55978[OCPBUGS-55978])
+
 [id="ocp-hosted-control-planes-4-19-known-issues_{context}"]
 
 [id="ocp-4-19-asynchronous-errata-updates_{context}"]