And the ipfailover pieces use that, so you can see an example of how to use it at: https://docs.openshift.com/enterprise/3.1/admin_guide/high_availability.html#configuring-a-highly-available-routing-service
Skip the ipfailover bits: the node labelling step 1 and then step 4 and 5in that section is what you'd need. HTH On Tue, Feb 9, 2016 at 11:28 AM, Paul Weil <[email protected]> wrote: > You may use node selectors to force the router to a particular node. This > is done with the --selector option of the oadm router command. > > For more information on scheduler configuration please see: > https://docs.openshift.org/latest/admin_guide/scheduler.html > > > On Tue, Feb 9, 2016 at 2:14 PM, Rishi Misra <[email protected]> > wrote: > >> I looked at >> https://github.com/openshift/origin/blob/master/docs/routing.md - >> section on deploying router manually - and it noted "To run the router >> manually (outside of a pod) you should first build the images with >> instructions found below". >> >> I had already build my router images but did not see specific >> instructions indicated above. When I tried to run the router in docker >> container I was unable to reach my apps (503 - service unavailable). I >> must be doing something wrong but cannot spot it. Any pointers appreciated. >> >> Alternatively, is there a way to peg router to a specific node so that I >> can configure my DNS entry accordingly? >> >> Thanks. >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > -- Ram// main(O,s){s=--O;10<putchar(3^O?97-(15&7183>>4*s)*(O++?-1:1):10)&&\ main(++O,s++);}
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
