cannot complete lab 10.1

echouserdevnull

using lab v2018-11-13

ive run through this a couple times, removing the created resources from the cluster and reapplying. when i attempt to complete step 11, i do not get a response from the load balancer. i can query the deployment successfully.

# k get ingresses.extensions ingress-test 
NAME           HOSTS             ADDRESS   PORTS   AGE
ingress-test   www.example.com             80      2d22h

i believe the failure is related to the lack of a bound address above (though i could be wrong, obv). netstat/lsof show no bound listeners on port 80 on any interface.

im using a 3 virtualbox instances on OSX, deployed with kubectl - one (untainted) master and two worker nodes.

can someone help me understand whats going on here?

echouserdevnull

none of the interfaces on the kube master or worker instances match 10.128.x.x.

i can query the pod address (10.38.x.x), and the service address(10.106.x.x) and get the nginx response. neither of these require the header to bet set to succeed. when i attempt to query either of the virtualized phyiscal nics, the curl fails.

i have to set up port forwarding to query the vbox host IP, which i havent done because neither virtual nic is answering, so i dont know where to send the traffic.

echouserdevnull

To test that you send the header to port 80 of the primary interface IP, not the pod directly. Does that work, if not what error do you get if any?

this is where it is failing, per above. i get a connection refused message on the master node. it looks like it works if i query the worker node directly it works after deleting and redeploying (i didnt taint the master to run pods). it might have done that before, i dont recall if i tested that or not.

If neither vnic is answering it sounds like an issue with VirtualBox network settings. My guess would be routing. When you query the primary interface, port 80 and using the suggested header, from one node to the other do you get a 404 response, or passed along to the expected service?

when i query the worker nodes, the 404 occurs correctly if the header is omitted from the curl, so i think that means its working correctly?

i might be misunderstanding how the loadbalancer is supposed to work - should any node in the cluster be able to route those queries, or only the nodes running the pod?

echouserdevnull

Ok that makes sense. it looks like i dont have a traefik controller running on my master because its untainted. the worker nodes running traefik work as described in the exercise.

so i think this is mostly my environment not matching the initial cluster exactly.