-
Story
-
Resolution: Done
-
Major
-
builds-1.0
-
None
-
2
-
False
-
None
-
False
-
SECFLOWOTL-27 - Shared Resource CSI Driver GA
-
-
-
1
-
Builds Sprint #6, Builds Sprint #7
User Story
As a cluster admin trying to install Builds for OpenShift I want to easily recognize the operator when installing it in OperatorHub
Background and Approach
Our initial launch of Builds for OpenShift had several areas of improvement related to its appearance in OperatorHub. This was documented in BUILD-845 - namely:
- We aren't using the Technology icon for the product
- Product name needs a capitalization in OperatorHub
- Documentation links should go to the product docs, not upstream docs.
- Emails should be Red Hat emails for support/triage.
Approach:
- Update the CSV for the new OpenShift Builds operator
Out of scope
- Fixing behavior related to default installation namespace.
- Fixing "day 2" action required by admin to install Shipwright Build
Dependencies
Definition of Done/ Acceptance Criteria
- Use the new Technology Icon (base64 encoded) in our operator CSV
- Ensure the name is "Builds for OpenShift" (capitalize the "B")
- Documentation links in CSV to go to official OpenShift documentation
- Emails for contact/support must go to Red Hat email addresses that are triaged by CEE: support@redhat.com
- Verify behaviors in a release candidate build