Bug 2306117 - OpenShift 4.13+ on vSphere the default storageclass should be thin-csi instead of thin for dynamic storage devices
Summary: OpenShift 4.13+ on vSphere the default storageclass should be thin-csi instea...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.13
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kusuma
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-20 14:45 UTC by Kevin Niederwanger
Modified: 2024-11-04 06:26 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-9482 0 None None None 2024-11-04 06:26:23 UTC

Description Kevin Niederwanger 2024-08-20 14:45:19 UTC 
Describe the issue: On OpenShift 4.13+ for vSphere the CSI migration is automatically enabled (https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/persistent-storage-csi-migration.html). Consequently, on a fresh deployment the `thin` storageclass will not be available anymore. Instead the `thin-csi` storageclass is available. 

Describe the task you were trying to accomplish: Deploy ODF on vSphere with dynamic storage devices

Suggestions for improvement: All documentation for ODF 4.13+  for vSphere with dynamic storage devices shall have `thin-csi` instead of `thin` as the default storageclass.

Document URL: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.13/html-single/deploying_openshift_data_foundation_on_vmware_vsphere/index#creating-an-openshift-data-foundation-service_cloud-storage

Chapter/Section Number and Title: 2.4. Creating an OpenShift Data Foundation cluster

Product Version: 4.13+

Environment Details:

Any other versions of this document that also needs this update: 4.14, 4.15, 4.16, ...

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