Bug 2155317 - From 4.10 all freshly installed clusters will deploy HPP CSI only
Summary: From 4.10 all freshly installed clusters will deploy HPP CSI only
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Documentation
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Audrey Spaulding
QA Contact: Oded Ramraz
URL:
Whiteboard: bug tracker 4.13
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-20 19:29 UTC by Kevin Alon Goldblatt
Modified: 2023-04-05 05:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-05 05:17:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-23499 0 None None None 2022-12-20 19:33:53 UTC

Description Kevin Alon Goldblatt 2022-12-20 19:29:37 UTC
Document URL: 
https://docs.openshift.com/container-platform/4.11/virt/virtual_machines/virtual_disks/virt-configuring-local-storage-for-vms.html

Section Number and Name: 
Configuring local storage for virtual machines 

Describe the issue: 
From 4.10 all freshly installed clusters will deploy HPP CSI only
But Legacy HPP will remain for those who upgraded 4.9->4.10...

For 4.10 the documentation is correct - where we talk about 4.9 -> 4.10 upgrade. But in 4.11, 4.12 and later we should only talk about HPP CSI, with no regard to upgrade and no regard to the Legacy HPP

Suggestions for improvement: 
Remove any mention of Legacy HPP
4.11 Documentation should reflect that newly installed clusters will only deploy HPP CSI
Additional information:

The same change should be documented in 4.12

Comment 1 Audrey Spaulding 2023-02-09 18:17:39 UTC
Status: Green

Comment 2 Audrey Spaulding 2023-02-17 14:16:25 UTC
Status: Green

Comment 3 Audrey Spaulding 2023-02-23 17:09:01 UTC
Status: Green


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