When creating a route, that route is only accessible from the primary IP of the host (the one MicroShift defaults to as NodeIP only. This has two problems:

1. To access the route locally from the host, one needs to add a mapping from the route's hostname to the primary IP to `/etc/hosts`, but that IP isn't known before it's assigned for the first time and it may change later. Being able to access the route via the loopback interface by binding the router to 127.0.0.1 or 0.0.0.0 would help.
2. To access the route (only) from a secondary interface isn't possible.

It should be possible to specify the interface a router binds to.