Cause: The router wouldn't reload HAProxy after the initial sync if the last item of the initial list of any of the watched resources didn't reach the router to trigger the commit. This could be caused by a route being rejected for any reason (e.g. specifying a host claimed by another namespace).
Consequence: The router could be left in its initial state (without any routes configured) until another commit-triggering event occurred (e.g. a watch event).
Fix: The router always reloads after initial sync.
Result: Routes are available after the initial sync.