Bug 1925529

Summary: OCP DevConsole Topology has broken OSSM istio-ingressgrateway link
Product: OpenShift Container Platform Reporter: Matt Mahoney <mmahoney>
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED NOTABUG QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7CC: aballant, aos-bugs, jakumar, kconner, lponce, msaud, nmukherj
Target Milestone: ---Keywords: TestBlockerForLayeredProduct
Target Release: 4.8.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: 2021-04-29 13:11:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Topology View none

Description Matt Mahoney 2021-02-05 13:07:12 UTC 
Created attachment 1755221 [details]
Topology View

Description of problem:

OCP DevConsole Topology view of Openshift Service Mesh namespace istio-system shows an istio-ingressgateway node, with an active URL link. Clicking on that link does not render an application (i.e. broken link).


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

Tested on OCP 4.7 

How reproducible:

Steps to Reproduce:
1. Deploy Openshift Service Mesh Operators
   Reference: https://docs.openshift.com/container-platform/4.6/service_mesh/v1x/installing-ossm.html
2. Deploy OS Control Plane into istio-system namespace
3. In OCP console, switch from Administrator to Developer
4. Click Topology, and then select istio-system namespace
5. Click istio-ingressgateway URL link

Actual results:
Broken link

Expected results:
Link should properly render a valid Istio-Ingressgateway.

Additional info:
Comment 1 Mohammed Saud 2021-02-11 10:35:29 UTC 
Unsure if this is related to DevConsole.

The topology simply displays the URL of the route that exposes the deployment's service.

I get the same URL when using the cli:
oc get route istio-ingressgateway -n istio-system -o jsonpath='{.spec.host}'
Comment 2 Matt Mahoney 2021-04-26 19:47:44 UTC 
This issue persists in OCP 4.8.0-fc.1
Comment 3 cvogt 2021-04-28 20:17:17 UTC 
To be honest, I don't know what this page is supposed to display.
The topology is providing a link to the URL exposed on the route associated with the service. The displayed route is correct.
As mentioned in an earlier comment, it is the same route url as `oc get route istio-ingressgateway -n istio-system -o jsonpath='{.spec.host}'`

We will need to get the service mesh team involved.
Comment 4 Lucas Ponce 2021-04-29 08:50:19 UTC 
Note that istio-ingressgateway requires a Istio Gateway + VirtualService + DestinationRule to route an external request to an internal service within the cluster.

So, if that configuration is not present, a default route to the istio-ingressgateway will show the result that is described in this BZ.

Typically, Istio users define multiple DNS to a public IP where the istio-ingressgateway is located, and those different hosts resolutions and routes are handled by the Istio Ingress Gateway.
Comment 7 kconner 2021-04-29 15:50:10 UTC 
While there is a route defined for the ingress gateway there is no guarantee there would be anything meaningful to link to so removing the link would be the best option.  How is this done?
Comment 12 cvogt 2021-04-30 18:07:13 UTC 
I have created a feature request for the dev console to evaluate adding a means for providing control over this link in topology.
See https://issues.redhat.com/browse/ODC-5805

As it stands now, the link is doing what it is meant to do; reflecting the URL of the associated route. As such I will be closing this issue in lieu of the feature request.