Description of problem: Sharded routers based on project namespace labels take too long to register a route. It can take around 7 minutes for the router to register a newly exposed route within a namespace. Version-Release number of selected component (if applicable): v3.6.131 How reproducible: Always. Steps to Reproduce: https://asciinema.org/a/sMCJJ6ThrthFpQdVADG6Gy5YK Actual results: Routes take too long to register based on NAMESPACE_LABELS. Expected results: Near "immediate" registration of an exposed route on a NAMESPACE_LABELS-sharded router, just as it happens when using ROUTE_LABELS. Additional info: You can fast forward to end of the recording to see how long it can take for a route to become exposed.
Can you confirm that it is only when route is created on a newly created project? On an existing project (one that has synced in ~10 minutes) the routes appear as quickly as in a non-sharded router. If yes, this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1355711
(In reply to Rajat Chopra from comment #1) > Can you confirm that it is only when route is created on a newly created > project? Yes, this is correct. Also, if I wait for the routes to be exposed correctly (those max ~10 minutes), I delete the project and re-create the project under the same name, the routes are exposed correctly immediately. So this only seems to affect completely new namespaces for which routes have not been resynced with the router. So, yes a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1355711.
Also duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1479295
*** This bug has been marked as a duplicate of bug 1479295 ***