Skip to content

Commit

Permalink
Rel notes for storage 4.18
Browse files Browse the repository at this point in the history
  • Loading branch information
Lisa Pettyjohn committed Jan 1, 2025
1 parent 66fb919 commit 955e319
Showing 1 changed file with 97 additions and 16 deletions.
113 changes: 97 additions & 16 deletions release_notes/ocp-4-18-release-notes.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,6 @@ This release adds improvements related to the following components and concepts:
[discrete]
[id="ocp-release-notes-ibm-z-power-support-matrix_{context}"]
=== {ibm-power-title}, {ibm-z-title}, and {ibm-linuxone-title} support matrix

Starting in {product-title} 4.14, Extended Update Support (EUS) is extended to the {ibm-power-name} and the {ibm-z-name} platform. For more information, see the link:https://access.redhat.com/support/policy/updates/openshift-eus[OpenShift EUS Overview].

.{product-title} features
Expand Down Expand Up @@ -474,9 +473,72 @@ The terminology for the `ip_whitelist` and `ip_blacklist` annotations have been

[id="ocp-4-18-storage-editing-overprovisioning-ratio_{context}"]
==== Over-provisioning ratio update after LVMCluster custom resource creation

Previously, the `thinPoolConfig.overprovisionRatio` field in the `LVMCluster` custom resource (CR) could be configured only during the creation of the `LVMCluster` CR. With this release, you can now update the `thinPoolConfig.overprovisionRatio` field even after creating the `LVMCluster` CR.

[id="ocp-4-18-release-notes-storage-cifs-smb-csi-driver_{context}"]
==== Persistent storage using CIFS/SMB CSI Driver Operator is generally available
{product-title} is capable of provisioning persistent volumes (PVs) with a Container Storage Interface (CSI) driver for the Common Internet File System (CIFS) dialect/Server Message Block (SMB) protocol. The CIFS/SMB CSI Driver Operator that manages this driver was introduced in {product-title} 4.16 with Technology Preview status. In {product-title} 4.18, it is now generally available.

For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-smb-cifs.adoc#persistent-storage-csi-smb-cifs[CIFS/SMB CSI Driver Operator].

[id="ocp-4-18-release-notes-storage-secret-csi-driver_{context}"]
==== Secret Store CSI Driver Operator is generally available
The Secrets Store Container Storage Interface (CSI) Driver Operator, `secrets-store.csi.k8s.io`, allows {product-title} to mount multiple secrets, keys, and certificates stored in enterprise-grade external secrets stores into pods as an inline ephemeral volume. The Secrets Store CSI Driver Operator communicates with the provider using gRPC to fetch the mount contents from the specified external secrets store. After the volume is attached, the data in it is mounted into the container’s file system. The Secrets Store CSI Driver Operator was available in {product-title} 4.14 as a Technology Preview feature. {product-title} 4.18 introduces this feature as generally available. For more information about the Secrets Store CSI driver, see xref:../storage/container_storage_interface/persistent-storage-csi-secrets-store.adoc#persistent-storage-csi-secrets-store[Secrets Store CSI Driver Operator].

// For information about using the Secrets Store CSI Driver Operator to mount secrets from an external secrets store to a CSI volume, see xref:../nodes/index#nodes-pods-secrets-store[Providing sensitive data to pods by using an external secrets store].

[id="ocp-4-18-release-notes-storage-pv-last-phase-transition-time_{context}"]
==== Persistent volume last phase transition time parameter is generally available
{product-title} 4.16 introduced a new parameter, `LastPhaseTransitionTime`, which has a timestamp that is updated every time a persistent volume (PV) transitions to a different phase (`pv.Status.Phase`). For {product-title} 4.18, this feature is generally available.

For more information about using the persistent volume last phase transition time parameter, see xref:../storage/understanding-persistent-storage.adoc#persistent-volumes_understanding-persistent-storage[Persistent volumes].

[id="ocp-4-18-release-notes-storage-volume-multi-vcenter-support_{context}"]
==== Multiple vCenter support for vSphere CSI is generally available
{product-title} 4.17 introduced the ability to deploy {product-title} across multiple vSphere clusters (vCenters) as a Technology Preview feature. In {product-title} 4.18, Multiple vCenter support is now generally available.

For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-multi-vcenter-support-overview_persistent-storage-csi-vsphere[Multiple vCenter support for vSphere CSI] and xref:../installing/installing_vsphere/installation-config-parameters-vsphere.adoc[Installation configuration parameters for vSphere].

[id="ocp-4-18-release-notes-storage-always-honor-reclaim-policy_{context}"]
==== Always apply persistent volume reclaim policy (Technical Preview)
Prior to {product-title} 4.18, the persistent volume (PV) reclaim policy was not always honored.

For a bound PV-persistent volume claim (PVC) pair, the ordering of PV-PVC deletion determined whether the PV delete reclaim policy was applied or not. The PV applied the reclaim policy if the PVC was deleted prior to deleting the PV. However, if the PV was deleted prior to deleting the PVC, then the reclaim policy was not applied. As a result of that behavior, the associated storage asset in the external infrastructure was not removed.

With {product-title} 4.18, the PV reclaim policy is consistently always applied. This feature has Technical Preview status.

For more information, see xref:../storage/understanding-persistent-storage.adoc#reclaiming_understanding-persistent-storage[Reclaim policy for persistent volumes].

[id="ocp-4-18-release-notes-storage-lso-cleanup_{context}"]
==== Improved ability to easily remove LVs or LVSs is generally available
{product-title} 4.18 improves the ability to remove Local Volumes (LVs) and Local Volume Sets (LVSs) by automatically removing artifacts, thus reducing the number of steps required.

For more information, see xref:../storage/persistent_storage/persistent_storage_local/persistent-storage-local.adoc#local-removing-device_persistent-storage-local[Removing a local volume or local volume set].

[id="ocp-4-18-release-notes-storage-volume-group-snapshots_{context}"]
==== CSI volume group snapshots is generally available
{product-title} 4.18 introduces Container Storage Interface (CSI) volume group snapshots as a generally available feature. CSI volume group snapshots use a label selector to group multiple persistent volume claims (PVCs) for snapshotting. A volume group snapshot represents copies from multiple volumes that are taken at the same point-in-time. This can be useful for applications that contain multiple volumes.

{product-title} supports volume group snapshots by default. However, the only storage type in {product-title} that supports volume group snapshots is {rh-storage}.

//For more information about CSI volume group snapshots, see xref:/../storage/container_storage_interface/persistent-storage-csi-group-snapshots.adoc#persistent-storage-csi-group-snapshots[CSI volume group snapshots].

[id="ocp-4-18-release-notes-storage-c3-n4-instance-types-hyperdisk_{context}"]
==== GCP PD CSI driver supports the C3 instance type for bare metal and N4 machine series is generally available
The Google Cloud Platform Persistent Disk (GCP PD) Container Storage Interface (CSI) driver supports the C3 instance type for bare metal and N4 machine series. The C3 instance type and N4 machine series support the hyperdisk-balanced disks.

Additionally, hyperdisk storage pools are supported for large-scale storage. A hyperdisk storage pool is a purchased collection of capacity, throughput, and IOPS, which you can then provision for your applications as needed.

For {product-title} 4.18, this feature is generally available.

//For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-gcp-pd.adoc#c3-instance-type-for-bare-metal-and-n4-machine-series[C3 instance type for bare metal and N4 machine series].

[id="ocp-4-18-release-notes-storage-openstack-manila-resize-support_{context}"]
==== OpenStack Manila expanding persistent volumes is generally supported
In {product-title} 4.18, OpenStack Manila supports expanding Container Storage Interface (CSI) persistent volumes (PVs). This feature is generally available.

For more information, see xref:../storage/expanding-persistent-volumes.adoc#expanding-persistent-volumes[Expanding persistent volumes] and xref:../storage/container_storage_interface/persistent-storage-csi.adoc#csi-drivers-supported_persistent-storage-csi[CSI drivers supported by {product-title}].

[id="ocp-release-notes-web-console_{context}"]
=== Web console

Expand Down Expand Up @@ -768,6 +830,11 @@ In the following tables, features are marked with the following statuses:
|General Availability
|Removed
|Removed

|Shared Resources CSI Driver Operator
|Technical Preview
|Deprecated
|Removed
|====

[discrete]
Expand Down Expand Up @@ -821,6 +888,10 @@ In the following tables, features are marked with the following statuses:
[id="ocp-4-18-removed-features_{context}"]
=== Removed features

[id="ocp-4-18-removals-storage_{context}"]
==== The Shared Resource CSI Driver is removed
The Shared Resource CSI Driver feature is now removed from {product-title} 4.18. It was deprecated in {product-title} 4.17. This feature is now generally available in Builds for Red Hat OpenShift 1.1. To use this feature, ensure you are using Builds for Red Hat OpenShift 1.1 or later.

[id="ocp-4-18-future-deprecation_{context}"]
=== Notice of future deprecation

Expand Down Expand Up @@ -1591,7 +1662,7 @@ In the following tables, features are marked with the following statuses:

|AWS EFS storage CSI usage metrics
|Not Available
|Not Available
|General Availability
|General Availability

|Automatic device discovery and provisioning with Local Storage Operator
Expand All @@ -1601,16 +1672,11 @@ In the following tables, features are marked with the following statuses:

|Azure File CSI snapshot support
|Not Available
|Not Available
|Technology Preview

|{ibm-power-server-name} Block CSI Driver Operator
|General Availability
|General Availability
|General Availability
|Technology Preview

|Read Write Once Pod access mode
|Technology Preview
|General Availability
|General Availability
|General Availability

Expand All @@ -1622,32 +1688,47 @@ In the following tables, features are marked with the following statuses:
|{secrets-store-operator}
|Technology Preview
|Technology Preview
|Technology Preview
|General Availability

|CIFS/SMB CSI Driver Operator
|Not Available
|Technology Preview
|Technology Preview
|General Availability

|VMWare vSphere multiple vCenter support
|Not Available
|Not Available
|Technology Preview
|General Availability

|Disabling/enabling storage on vSphere
|Not Available
|Not Available
|Technology Preview
|Technology Preview

|RWX/RWO SELinux Mount
|Not Available
|Not Available
|Developer Preview
|Developer Preview

|Migrating CNS Volumes Between Datastores
|Not Available
|Not Available
|Developer Preview
|Developer Preview

|CSI volume group snapshots
|Not Available
|Not Available
|General Availability

|GCP PD supports C3/N4 instance types and hyperdisk-balanced disks
|Not Available
|Not Available
|General Availability

|OpenStack Manila support for CSI resize
|Not Available
|Not Available
|General Availability

|====

Expand Down

0 comments on commit 955e319

Please sign in to comment.