Bug 1836177

"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.