Adding Annette as she is testing the feature and it would be good to get her views on the content
This bug is for the minimal deployment procedure which is basically being tested by UAT team @olakra https://bugzilla.redhat.com/show_bug.cgi?id=1886541 is now fixed in OCP 4.6.z and the bug also has the screenshots attached with how the trigger message will look like (both for internal and internal-attached) Only problem is - the screenshot is from AWS I3 clusters. Please confirm with Annette what screenshots we would like to use.
> @Rohan can the localvolume CR still be used? Yes, LocalVolume apis are still valid.
Sounds good to me.
looking at the 2 links provided in https://bugzilla.redhat.com/show_bug.cgi?id=1880917#c23 and both are for generic deployment of LSO on VMware and BM and do not mention the planning guide for deploying with minimum nodes
Moving to VERIFIED based on https://bugzilla.redhat.com/show_bug.cgi?id=1880912#c5 Chapter 1.3. Creating an OpenShift Container Storage Cluster Service in internal mode: "If the nodes selected do not match the OpenShift Container Storage cluster requirement of an aggregated 30 CPUs and 72 GiB of RAM, a minimal cluster will be deployed. For minimum starting node requirements, see Resource requirements section in Planning guide."