Bug 1967047: Add new HealthState to signify an operator is upgradable in the cluster dashboard

[jcaianirh]

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1967047

Added a new HealthState called upgradable which shows whether an operator has an upgrade available. The previous fix to this bug didn't change the health state which was pending (but the install wasn't pending). I played with using the existing warning state which is possible. I ended up creating this new upgradable state which shows the blue up arrow icon in the dashboard to show there is an upgrade available.

cc: @openshift/team-ux-review

[openshift-ci]

@jcaianirh: This pull request references Bugzilla bug 1967047, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.9.0) matches configured target release for branch (4.9.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @yanpzhan

In response to this:

Bug 1967047: Add new HealthState to signify an operator is upgradable in the cluster dashboard

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[itsptk]

@jcaianirh If a different operator is in a warning or error state, do those states take precedence in the "overall" status shown on the dashboard status card? This otherwise looks good to me.

[spadgett]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaianirh, spadgett

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [spadgett]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@jcaianirh: All pull requests linked via external trackers have merged:

• openshift/console#9264
• openshift/console#9475

Bugzilla bug 1967047 has been moved to the MODIFIED state.

In response to this:

Bug 1967047: Add new HealthState to signify an operator is upgradable in the cluster dashboard

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jcaianirh]

@jcaianirh If a different operator is in a warning or error state, do those states take precedence in the "overall" status shown on the dashboard status card? This otherwise looks good to me.

Yes, @itsptk the error states take precedence over the upgrade available. Here is a snapshot of that case where i have one manual subscription operator with an upgrade available, but also another operator with an error status.