cannot complete lab 10.1
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?
Comments
-
Hello,
Thank you for the detailed question. It helps try to troubleshoot. In this case you mention not getting a response from a load balancer, do you mean the load balancer service? Only if you have an external load balancer would you get that IP entry. If you send curl -H "Host: www.example.com" http://10.128.xx.yy/ where you replace the .xx.yy with your IP, do you get a nginx web server response?
When you try the same curl but to the public IP of your VMs (which may be the same, I don't know what networking options you configured in VirtualBox) is it different?
Regards,
0 -
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.
0 -
Hello,
If you are not getting a 404 error, which would indicate you are reaching the ingress controller, but it is not configured to pass along the message to the proper back-end service.
If a query to the ClusterIP works and the Pod we know the web server container is running and responding to messages. Next would be to test the ingress controller. 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?
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?
Regards,
0 -
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?
0 -
Hello,
The way that Calico works is that iptables rules are updated on every node. Regardless of which worker node you make the request to,
External-IP:High-Port-Number
the combination of iptables and Calico will get the request to the pod, even if the pod is running on a different worker.The LoadBalancer service type is a NodePort plus an asynchronous request to use an exterior load balancer. If one has not been configured on the exterior there is no response. The kubectl svc get output shows a "Pending" in the exterior IP field. To be more clear the creation of a load balancer does not create a load balancer, it only requests to use one.
If the worker nodes respond to its public IP and port 80 when the request is from within the node it would narrow down if the issue is with the ingress controller OR the networking external to the node.
If you query your outside facing IP address port 80 from within the node, and you still do not get at least a 404 then the issue is with the ingress controller.
If that works (You get the expected web page or at least a 404) we know the ingress controller is working so if you cannot get the same from outside the node then it is the networking of your virtualization choice.
Regards,
0 -
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.
0
Categories
- All Categories
- 219 LFX Mentorship
- 219 LFX Mentorship: Linux Kernel
- 793 Linux Foundation IT Professional Programs
- 354 Cloud Engineer IT Professional Program
- 179 Advanced Cloud Engineer IT Professional Program
- 82 DevOps Engineer IT Professional Program
- 147 Cloud Native Developer IT Professional Program
- 137 Express Training Courses
- 137 Express Courses - Discussion Forum
- 6.2K Training Courses
- 47 LFC110 Class Forum - Discontinued
- 71 LFC131 Class Forum
- 42 LFD102 Class Forum
- 226 LFD103 Class Forum
- 19 LFD110 Class Forum
- 38 LFD121 Class Forum
- 18 LFD133 Class Forum
- 7 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 5 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 697 LFD259 Class Forum
- 111 LFD272 Class Forum
- 4 LFD272-JP クラス フォーラム
- 12 LFD273 Class Forum
- 149 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 2 LFS116 Class Forum
- 4 LFS118 Class Forum
- LFS120 Class Forum
- 7 LFS142 Class Forum
- 5 LFS144 Class Forum
- 4 LFS145 Class Forum
- 3 LFS146 Class Forum
- 3 LFS147 Class Forum
- 1 LFS148 Class Forum
- 15 LFS151 Class Forum
- 2 LFS157 Class Forum
- 30 LFS158 Class Forum
- 7 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 32 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム
- 18 LFS203 Class Forum
- 134 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 2 LFS245 Class Forum
- LFS246 Class Forum
- 49 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 153 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 9 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 119 LFS260 Class Forum
- 159 LFS261 Class Forum
- 42 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 24 LFS268 Class Forum
- 30 LFS269 Class Forum
- LFS270 Class Forum
- 202 LFS272 Class Forum
- 2 LFS272-JP クラス フォーラム
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 9 LFW111 Class Forum
- 259 LFW211 Class Forum
- 181 LFW212 Class Forum
- 13 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 796 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 103 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 758 Linux Distributions
- 82 Debian
- 67 Fedora
- 17 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 353 Ubuntu
- 468 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 63 Mobile Computing
- 18 Android
- 33 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 371 Off Topic
- 114 Introductions
- 174 Small Talk
- 22 Study Material
- 805 Programming and Development
- 303 Kernel Development
- 484 Software Development
- 1.8K Software
- 263 Applications
- 183 Command Line
- 3 Compiling/Installing
- 987 Games
- 317 Installation
- 97 All In Program
- 97 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)