Bug 2189477 - Change in Local Storage Operator channels in docs
Summary: Change in Local Storage Operator channels in docs
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-25 11:46 UTC by Miguel Blach
Modified: 2023-08-09 16:43 UTC (History)
2 users (show)

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

Attachments (Terms of Use)

Description Miguel Blach 2023-04-25 11:46:46 UTC 
Describe the issue:

In ODF documentation page: https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.11/html-single/deploying_openshift_data_foundation_using_bare_metal_infrastructure/index#installing-local-storage-operator_local-bare-metal

~~~
Update channel as either 4.11 or stable.
~~~

Currently the Local Storage Operator(LSO), only uses "stable" as a channel in version 4.11+: https://issues.redhat.com/browse/OCPBUGS-5902


Describe the task you were trying to accomplish:

Avoid confusing operator channels when using the documentation

Suggestions for improvement:

Update the LSO channel in the documentation to reflect the latest changes.

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.11/html-single/deploying_openshift_data_foundation_using_bare_metal_infrastructure/index#installing-local-storage-operator_local-bare-metal

Chapter/Section Number and Title:

Product Version: 4.11

Environment Details:

Any other versions of this document that also needs this update:

- In version 4.12 I see the same as in 4.11, would need to be updated too.
- Probably in all related version that use LSO as part of the deployment methods.

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