Bug 1848271

Summary:	Show only one Kibana Console Link in App Navbar
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Logging	Assignee:	Periklis Tsirakidis <periklis>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	aos-bugs, jcantril
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:44:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1847450
Bug Blocks:

Description OpenShift BugZilla Robot 2020-06-18 06:26:41 UTC

+++ This bug was initially created as a clone of Bug #1847450 +++

Description of problem:
We used to publish two links via ConsoleLink CR for kibana without specific distinction which link is for the Admin and which for the Developer view. Since the links are published by the web console in the new App Navbar ([1]), this results in two identical links. 

Expected Behavior:
Publish only on link for Kibana on the App navbar.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1840478#c1

--- Additional comment from jcantril on 2020-06-16 13:56:10 UTC ---

Needs a 4.5.z backport

Comment 4 Anping Li 2020-06-23 03:34:43 UTC

$verified on clusterlogging.4.5.0-202006201517. Only one consolelink now. and user can be redirected to kibana from console.

oc get ConsoleLink
NAME                        TEXT              URL                                                                            MENU   AGE
kibana-public-url           Logging           https://kibana-openshift-logging.apps.anli456221.qe.devcluster.openshift.com          80m

Comment 5 errata-xmlrpc 2020-07-13 17:44:18 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