Rel notes for storage 4.18 #86629
Open
Rel notes for storage 4.18 #86629
+97
−16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
the
size/L
lpettyjo
added
branch/enterprise-4.18
peer-review-needed
|
🤖 Wed Jan 01 19:41:10 - Prow CI generated the docs preview: |
lpettyjo
force-pushed
the
rel_notes_4_18
branch
2 times, most recently
from
82f709a to
49f2929
Compare
xenolinux
added
peer-review-in-progress
xenolinux
reviewed
Dec 31, 2024
xenolinux
added
peer-review-done
lpettyjo
force-pushed
the
rel_notes_4_18
branch
from
49f2929 to
955e319
Compare
|
@lpettyjo: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Phaow
reviewed
Jan 2, 2025
| @@ -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. | |||
There was a problem hiding this comment.
Suggested change
| 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. | |
| The Shared Resource CSI Driver feature was deprecated in {product-title} 4.17 and is now removed from {product-title} 4.18. |
Maybe better.
duanwei33
reviewed
Jan 2, 2025
| ==== 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]. |
There was a problem hiding this comment.
It's not the scope of this RN PR, but let's ensure we update the reference Multiple vCenter support for vSphere CSI to remove the TP.
| 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 |
There was a problem hiding this comment.
The content looks good, but please note the code is still not ready now and we need to recheck this part before release.
ropatil010
reviewed
Jan 2, 2025
| 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 |
There was a problem hiding this comment.
Content looks good to me for Secret Store part.
Double confirm "to mount multiple secrets, keys, and certificates stored" => "to mount multiple secrets, keys and certificates stored" would be better?
radeore
reviewed
Jan 2, 2025
|
|
||
| [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. |
radeore
reviewed
Jan 2, 2025
| ==== 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]. |
There was a problem hiding this comment.
This reference takes to PV docs, but doesn't have details about "last phase transition time parameter"
radeore
reviewed
Jan 2, 2025
| ==== 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. |
There was a problem hiding this comment.
Suggested change
| 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. | |
| For a bound persistent volume (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. |
radeore
reviewed
Jan 2, 2025
| 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) |
There was a problem hiding this comment.
Suggested change
| ==== Always apply persistent volume reclaim policy (Technical Preview) | |
| ==== Always honor persistent volume reclaim policy (Technical Preview) |
There was a problem hiding this comment.
In case to keep title consistent with Upstream feature
radeore
reviewed
Jan 2, 2025
|
|
||
| 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. |
There was a problem hiding this comment.
Should we have this feature listed under "Storage TechPreview features" table? cc. @duanwei33
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version(s): 4.18
Issue:
Link to docs preview:
Feature blurbs: https://86629--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html#ocp-release-notes-storage_release-notes
Tech Preview status: https://86629--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html#ocp-4-18-technology-preview-tables_release-notes
Removed features: https://86629--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html#ocp-4-18-removed-features_release-notes
QE review:
Additional information:
PTAL: @gcharot @jsafrane @dobsonj @gnufied @dfajmon @vr4manta @RomanBednar @mpatlasov @gouthampacha @skopacz1 @rlobillo @Phaow @ropatil010 @wsun1 @chao007 @duanwei33 @radeore