Bug 1827638 - CRD named 'Driver' is misleading
Summary: CRD named 'Driver' is misleading
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.0
Assignee: Jan Safranek
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-24 12:09 UTC by Jan Safranek
Modified: 2020-07-13 17:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:31:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift aws-ebs-csi-driver-operator pull 50 0 None closed Bug 1827638: Rename CRD to AWSEBSDriver 2020-07-01 09:12:34 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:28 UTC

Description Jan Safranek 2020-04-24 12:09:05 UTC
Description of problem:

Currently, AWS EBS CSI driver operator uses CRD named "Driver" in API group "ebs.aws.csi.openshift.io". In the future, we want to add many other drivers (GCE PD, OpenStack Cinder, vShpere Disk, Azure Disk, Azure File, ...) and using 'Driver' as the CRD name for them would be confusing.

What would "oc get driver" do, especially when more CSI driver operators are installed?

The operator should use CRD unique for the operator. We decided to use "AWSEBSDriver" CRD in "csi.openshift.io" API group. So "oc get awsebsdriver".

Comment 3 Qin Ping 2020-05-09 11:37:00 UTC
Verified with:
# oc get csv -n openshift-aws-ebs-csi-driver-operator
NAME                                 DISPLAY                VERSION   REPLACES
 PHASE
aws-ebs-csi-driver-operator.v4.5.0   AWS EBS CSI Operator   4.5.0             
 Succeeded

ose-aws-ebs-csi-driver-operator-bundle-container-v4.5-6

ose-aws-ebs-csi-driver-operator-container-v4.5-5

# oc get awsebsdriver -n openshift-aws-ebs-csi-driver-operator
NAME      AGE
cluster   22s

Comment 4 errata-xmlrpc 2020-07-13 17:31:14 UTC
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


Note You need to log in before you can comment on or make changes to this bug.