Bug 1889374 - Kiali feature won't work on fresh 4.6 cluster
Summary: Kiali feature won't work on fresh 4.6 cluster
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: cvogt
QA Contact: Gajanan More
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-19 13:54 UTC by Jaivardhan Kumar
Modified: 2021-01-15 12:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-01-11 04:17:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jaivardhan Kumar 2020-10-19 13:54:21 UTC
Description of problem: The availability of Kiali features in ODC are dependent on the availability of the Elastic search operator as Service Mesh operator depends on it. Currently this operator is not available on the fresh installation of OCP 4.6. However these features, are available when you upgrade OCP from a previous version to the latest.

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

How reproducible: Always

Steps to Reproduce:
1. Install Service Mesh operator
2. Create a name space and add some workloads
3. In topology can't see link to kiali

Actual results: Can't see Kiali link on topology

Expected results: Should see kiali link in topology

Additional info:

Comment 1 Vikram Raj 2020-11-02 14:48:41 UTC
I verified the Kiali feature by installing Elastic Search, Jaeger, Kiali, and Red Hat OpenShift Service Mesh operators on 4.6 cluster and it is working as expected.

Comment 3 Jaivardhan Kumar 2021-01-11 04:17:01 UTC
Marking it as closed as this is not a bug on ODC side as the fix was associated with operator not in ODC and this feature was dependent on it.

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