origin-web-console: Application route scoring picks the wrong route
The application route scoring algorithm is too enforcing and makes wrong assumptions about how an application would look like: https://github.com/openshift/origin-web-console/blob/master/app/scripts/services/routes.js#L106
The following is a simple microservices application which consists of three pods each with their own routes. A is the web pod, B and C provide REST APIs:
+---+
| A |
+---+
|
+---------+
| |
+-v-+ +-v-+
| C | | B |
+---+ +---+
The new UI picks one of the routes randomly since all three score the same while from the user’s perspective, route A is considered the application route and the entry point to this app.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 39 (15 by maintainers)
Everyone agrees on the issues here but all suggestions so far are rejected in favour of a better solution that has not presented itself yet 😃
Here is the summary of suggestions:
If it was to vote, I’d vote for (1) as the least obstructive solution.
hi, just found this issue but it is a pain point we are experiencing as well. we have an application with multiple pods grouped together and 2 of them have routes exposed, but we would like to have our users only use 1 of these routes.
we are currently trying to do some hackery to get it to display our preferred route, but this is non-ideal. i don’t quite follow the problems with letting the user select an annotation for the primary route, but some way to specify this would be greatly appreciated.
It’s not possible to create a scoring that matches the majority of cases since applications look widely different from team to team.
I’d suggest allowing users to label or annotate the main route to hint which one to pick. For example the it could first look for a route with label app-route=true and if not available then score the routes and pick one.
On Fri, 11 Aug 2017 at 22:30, Sam Padgett notifications@github.com wrote: