I also reproduce this on dev-preview-stg(online version 3.5.0.10)
xxing This requires a router docker container image built from these sources. The router image name in the router's dc must point to the new router docker image.
bbennett , what else info do you need? seems we need update to use the specific router image in this environment according to comment 2.
xxing I am not familiar with your test setup. The changes for the 503 message are in the router image. Please attach a copy of the haproxy-config.template file from the running router. oc rsh <router-pod> cat haproxy-config.template
The problem is that the openshift online custom template needs the same fix.
xxing the haproxy-config.temp file is different than origin. You might like to review the changes in origin and update your file.
I just checked, dev-preview-stg router pods have: - name: TEMPLATE_FILE value: /var/lib/haproxy/conf/custom/haproxy-config.template It appears you collected /var/lib/haproxy/config/haproxy-config.template instead of the /custom/ version, which is in use.
https://github.com/openshift/online/pull/1145
OpenShift Online Preview has been decommissioned, go to https://manage.openshift.com/ for using OpenShift Online starter cluster