"Create EBS CSI Driver" shows a wrong CR sample: Steps to Reproduce: 1. Install AWS EBS CSI driver operator through OLM (this may be hard, because it's scheduled to be released in 4.5, so the default OperatorHub does not have it yet) CRD + CSV: https://github.com/openshift/aws-ebs-csi-driver-operator/tree/master/bundle/manifests 2. Click: "Installed Operators" -> "EBS CSI Driver" in "Provided API column" -> "Create EBS CSI Driver" Actual results: This template shows up: apiVersion: csi.openshift.io/v1alpha1 kind: AWSEBSDriver metadata: name: example spec: {} Expected results: Template from CSV: apiVersion: csi.openshift.io/v1alpha1 kind: AWSEBSDriver metadata: name: cluster labels: {} spec: logLevel: Normal managementState: Managed operatorLogLevel: Normal Additional info: I get the correct sample when I go through "Installed Operators" -> "AWS EBS CSI Operator" -> "(+) Create Instance". I checked a random operator (Local Storage), it offers the same sample for both ways how to create the CR. The main difference is that the AWSEBSDriver CRs are not namespaced, while LocalVolumes are.
Simple way how to make AWS EBS operator available in OperatorHub: https://bugzilla.redhat.com/show_bug.cgi?id=1828958#c5
Created attachment 1691675 [details] Verification screenshot
The default YAML content of Create AWSEBSDriver view is as expected. Please refer to the screenshot. Verified on 4.5.0-0.nightly-2020-05-24-191212
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