Router doesn't immediately load existing routes on pod redeployement

Issue

• When the HAProxy pods are first created, they don't properly load the routes configured to start on them. This results in restarts of the Proxy pods resulting in serving 503 errors until they reload:

  [root@router1 ~]# docker logs -f $(docker ps | grep haproxy-router | cut -c1-12)
  I1010 07:35:16.929616       1 router.go:153] Router is only using routes in namespaces matching region=phx1,servicephase=qa,zone=internal
  I1010 07:35:17.131139       1 router.go:321] Router reloaded:
   - Checking HAProxy /healthz on port 1936 ...
   - HAProxy port 1936 health check ok : 0 retry attempt(s).
  W1010 07:37:00.928813       1 router.go:617] a edge terminated route with host master.example.com does not have the required certificates.  The route will still be created but no certificates will be written
  W1010 07:37:00.928857       1 router.go:617] a edge terminated route with host hello-world-syseng-validation.cloudapps.example.com does not have the required certificates.  The route will still be created but no certificates will be written
  I1010 07:37:00.987037       1 router.go:321] Router reloaded:
  

• The route propagation had stopped entirely on the routers after one master-api was down.