Description of problem (please be detailed as possible and provide log snippests): Make it possible for people to install ODF LVMO via OperatorHub. Version of all relevant components (if applicable): ODF 4.10 & 4.11 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Actual results: Currently we are unsure if LVMO will be listed and need confirmation Expected results: Make sure ODF LVMO is selectable and installable via OperatorHub. No further UI changes are needed beyond the install itself (we don't need to be able to create the LVMCluster CR via the UI) Additional info: As discussed with Nithya
turns out that this just works. There are two optimizations to the current way that are being worked on in https://bugzilla.redhat.com/show_bug.cgi?id=2083129 1) Put LVMO into the Storage section in OperatorHub 2) Mark openshift-storage as the recommended namespace In addition to the above we also want to mark the LVMCluster CR as requirement to use LVM Operator. This is being worked on in https://bugzilla.redhat.com/show_bug.cgi?id=2084116 Thus we can close this ticket here.
Removing need info.