Description of problem:
Inconsistent labels create confusion and delay tasks.
“Project” vs “Namespace”, “Install” vs “Subscribe”, “Member” vs “Pod”, etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
To install an operator, users first select “Install” button and then have to select the “Subscribe” button on the subsequent “Create Operator Subscription” page. The same action of installing an operator was labeled as “install”, “create subscription”, or “subscribe” in the same process flow.
Various labels for the same action
Users need clarification on whether they are installing or subscribing and understand the difference.
Clarified OCP version 4.3.0
The UI development team will need input from UX team, as to appropriate names/labels and wording that should be used in the specific user scenarios noted above.
I am changing the scope of this bug to just be the resolution of the "Install" & "Subscribe" terminology, as this would be the most specific to the operator installation area. I have captured this in design story [https://issues.redhat.com/browse/PD-377] and will work towards a design that more consistently uses these terms. I will link that design in this bug once complete.
I have captured the more widespread issue of project/namespace usage in design story: https://issues.redhat.com/browse/PD-422
I suspect the use of "member" instead of pod was specific to the etcd operator, and would require a change on the operator's part.
The updated design can be seen attached to https://issues.redhat.com/browse/PD-377
On the operator installation page:
Operator Subscription -> Operator Installation
Create Operator Subscription -> Install Operator
Subscribe (button) -> Install
Also the website page title: OperatorHub Subscription -> Operator Installation
Created attachment 1689736 [details]
Display correctly, attached the screenshot for refer.
Verified on 4.5.0-0.nightly-2020-05-19-011623
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.