In UI, when Argo renders a Route object box, it does not show the link to the URL it represents, as it happens to Ingress objects.
The same is true for a application box in Dashboard, which shows ingresses links, but not routes.
It seems to me that the problem is that Argo is not specifically aware of OpenShift objects.
Motivation
Make Argo better to use when integrated to OpenShift clusters.
Proposal
So far I had no synchronization problem with OpenShift, only UI problems. So I think that the way to go is to make the UI capable to distinguish some OpenShift objects, at least the most common ones, like DeploymentConfig and Route.
Summary
In UI, when Argo renders a Route object box, it does not show the link to the URL it represents, as it happens to Ingress objects. The same is true for a application box in Dashboard, which shows ingresses links, but not routes. It seems to me that the problem is that Argo is not specifically aware of OpenShift objects.
Motivation
Make Argo better to use when integrated to OpenShift clusters.
Proposal
So far I had no synchronization problem with OpenShift, only UI problems. So I think that the way to go is to make the UI capable to distinguish some OpenShift objects, at least the most common ones, like DeploymentConfig and Route.