Re: oc get route

2016-08-18 Thread Clayton Coleman
If you ssh to the host machine with the router container, and try to curl https://HOST_IP:80, do you get a response from the server? What about curling that same address from another machine? If not, generally that's firewall rules in play (or perhaps the router process is binding to the wrong

Re: oc get route

2016-08-17 Thread Sco
Unfortunately oc cluster up is not a solution that provides sufficient evaluation capability for our use. --all-namespaces returns: #oc get routes --all-namespaces NAMESPACE NAME HOST/PORT PATH SERVICETERMINATION LABELS

Re: oc get route

2016-08-16 Thread Rajat Chopra
Also check 'oc get routes --all-namespaces' just to rule out that the route got created in another namespace. Also, the traffic needs to be directed to the node where haproxy is running (not the master). If the route is not created then one needs to create it, not sure if the app you created at a

Re: oc get route

2016-08-16 Thread Jonathan Yu
Hi there, For development/test purposes, I think "oc cluster up" is the easiest way to get a cluster running. It simply requires a running docker daemon (and access to the docker socket, so you either need to be root or your user added to the "docker" group). There's a demonstration here: