per the bug #1827638, we prefer the CRD defined in csi-xxx-driver-operator uses the unified format, so the end-user can use CSI operator better.
Please use ManilaDriver in "csi.openshift.io" API group.
(In reply to Jan Safranek from comment #1) > Please use ManilaDriver in "csi.openshift.io" API group. Not an objection, just an observation: there is a non-csi Manila driver in upstream cloud-provider OpenStack through version 1.17, which is different than the Manila CSI driver that we are supporting downstream. It is not included in upstream cloud-provider-openstack starting with version 1.18. I mention this just in case anyone might confuse the two, but am not worried since this context is clearly CSI.
Verified pass with images in https://errata.devel.redhat.com/advisory/54130. [wduan@MINT verification-tests]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-06-10-201008 True False 23h Cluster version is 4.5.0-0.nightly-2020-06-10-201008 [wduan@MINT verification-tests]$ oc get maniladriver NAME AGE cluster 10h [wduan@MINT verification-tests]$ oc explain maniladriver KIND: ManilaDriver VERSION: csi.openshift.io/v1alpha1 DESCRIPTION: <empty>
Also from webconsole, the instance name is "ManilaDriver"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409