Yes, I set master as work nodes and as infra nodes. Thanks for your help. I understood this concept now.
Thanks, Jared, (韦煜） Software developer Interested in open source software, big data, Linux ________________________________ From: Akram Ben Aissi <akram.benai...@gmail.com> Sent: Tuesday, August 15, 2017 7:11:03 PM To: Yu Wei Cc: users@lists.openshift.redhat.com; d...@lists.openshift.redhat.com Subject: Re: HAProxy not running on master Hi Yui, the masters runs the OpenShift API and web console on port 8443. OpenShift CLI or nodes communicates with master on this port. OpenShift router are not really supposed to run on masters, unless you set your masters also as nodes, and specifically as infra nodes (region=infra) If you do so, then, indeed, you will have an additional HAProxy process running on masters and listening on ports 80 and 443. On 15 August 2017 at 12:47, Yu Wei <yu20...@hotmail.com<mailto:yu20...@hotmail.com>> wrote: Hi, I setup cluster with 1 lb, 2 masters and 2 work nodes. On host lb, haproxy service and openshift_loadbalancer was running. On master node, I found that haproxy was failed to start. And openshift/origin-haproxy-router was running with container name k8s_router.xxxxxxxxxxx. I also observed that on that master node many connections was established via port 8443. Is this expected behavior? Or anything goes wrong? Thanks, Jared, (韦煜） Software developer Interested in open source software, big data, Linux _______________________________________________ dev mailing list d...@lists.openshift.redhat.com<mailto:d...@lists.openshift.redhat.com> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
