Bug 2319358 - Managing guide Note for PVC resize support needs update
Summary: Managing guide Note for PVC resize support needs update
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Kusuma
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-17 11:33 UTC by Neha Berry
Modified: 2024-10-17 11:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-9401 0 None None None 2024-10-17 11:35:02 UTC

Description Neha Berry 2024-10-17 11:33:43 UTC
Describe the issue:
==========================
Current note in Managing guide

Note
PVC expansion is not supported for OSD, MON and encrypted PVCs.


1. We will support ODF resize from 4.16.3
2. Encrypted PVC resize is a Dev preview feature in 4.14 - This is a KCS: https://access.redhat.com/articles/7032032
3. Encrypted PVC resize for RBD is a GA feature in 4.15
https://issues.redhat.com/browse/RHSTOR-4872


So we would need the document Note to be updated accordingly in guides 4.14, 4.15, 4.16 , 4.17 



Slack discussion - https://ibm-systems-storage.slack.com/archives/C06DWD30QTZ/p1729068908603129






Document URL:
https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/managing_and_allocating_storage_resources/index

Chapter/Section Number and Title:
9.4. Expanding Persistent Volume Claims 



Product Version:
So we would need the document Note to be updated accordingly in guides 4.14, 4.15, 4.16 , 4.17 


Environment Details:

Any other versions of this document that also needs this update:
=================================================================
4.17, 4.15
Additional information:


Note You need to log in before you can comment on or make changes to this bug.