Bug 2037182 - PingSource badge color is not matched with knativeEventing color
Summary: PingSource badge color is not matched with knativeEventing color
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Vikram Raj
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-05 07:11 UTC by Vikram Raj
Modified: 2022-03-10 16:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:37:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
PingSource (82.15 KB, image/png)
2022-01-05 07:11 UTC, Vikram Raj
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10774 0 None open Bug 2037182: update the ping source apiVersion 2022-01-05 07:13:52 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:23 UTC

Description Vikram Raj 2022-01-05 07:11:05 UTC
Created attachment 1848993 [details]

Description of problem:
PingSource badge color is not matched with knativeEventing color

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a pingSource and navigate to topology

Actual results:
The badge color for PingSource badge is blue.

Expected results:
Badge color for PingSource should be brown which is the knativeEventing color.

Additional info:

Comment 5 spathak@redhat.com 2022-02-04 09:44:39 UTC
Verified on build version: 4.10.0-0.nightly-2022-02-04-015640
Browser: Google Chrome 97

Comment 7 errata-xmlrpc 2022-03-10 16:37:09 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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