Expected Behavior
Given a Route I would expect there to be a straightforward way to figure out what DNS maps to that route. For example, given a Route, you can't figure out from it how to access it externally because this is configured in the elaconfig and it makes it more difficult when trying to give this dns address to some other parts of the system (say external consumers of this particular service (route)).
Actual Behavior
You have to look at the route and spin through the labels and find the label selectors against elaconfig. and then figure out what domains match. Seems a bit clunky to me.
Steps to Reproduce the Problem
Additional Info
Expected Behavior
Given a Route I would expect there to be a straightforward way to figure out what DNS maps to that route. For example, given a Route, you can't figure out from it how to access it externally because this is configured in the elaconfig and it makes it more difficult when trying to give this dns address to some other parts of the system (say external consumers of this particular service (route)).
Actual Behavior
You have to look at the route and spin through the labels and find the label selectors against elaconfig. and then figure out what domains match. Seems a bit clunky to me.
Steps to Reproduce the Problem
Additional Info