Not clear if you want the router to automatically serve the 503 page or not. If you do, this line in the haproxy config template: https://github.com/openshift/origin/blob/master/images/router/haproxy/conf/haproxy-config.template#L198
automatically sends a 503 page if your service is down (example has 0 pods backing the service). The actual error page template is at: https://github.com/openshift/origin/blob/master/images/router/haproxy/conf/error-page-503.http You could customize the template and/or error page (and the router image) to use a different page. Alternatively, if you desire some other behavior, you can disable it by removing that haproxy directive. Does still need a custom template + router image. HTH. On Mon, Jun 6, 2016 at 12:58 PM, Philippe Lafoucrière < philippe.lafoucri...@tech-angels.com> wrote: > @Clayton: > Sorry for the confusion. I'm not updating the routeR, I'm updating the > route directly. The route to our website is pointing to a "maintenance" > service during maintenance. This service serves 503 pages for most URLs, > except a few for testing purprose. > > The problem is: If I browse my website, I get the expected 503 code, but a > blank page, instead of the desired maintenance page served by the > "maintenance" pods. I don't understand this blank page, it's like haproxy > is not forwarding it because the pods responded with a 503. > > @v: Can I use a dedicated router per project? > > Thanks > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > -- Ram// main(O,s){s=--O;10<putchar(3^O?97-(15&7183>>4*s)*(O++?-1:1):10)&&\ main(++O,s++);}
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
