Lab 2.1.10: ClusterIPs unreachable from Master to Minion
Would there be any reason that my ClusterIPs are not reachable from the Master node to pods running on the Minion? I made sure my AWS Security Group has TCP port 80 open:
ubuntu@ip-xxx-xx-xx-xxx:~$ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE basicservice ClusterIP 10.103.61.173 <none> 80/TCP 31m kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 56m ubuntu@ip-xxx-xx-xx-xxx:~$ curl http://10.103.61.173 ^C
I am able to reach the api server on the Master from the minion node.
ubuntu@ip-xxx-xx-xx-xxx:~$ curl --insecure https://10.96.0.1/api { "kind": "APIVersions", "versions": [ "v1" ], "serverAddressByClientCIDRs": [ { "clientCIDR": "0.0.0.0/0", "serverAddress": "xxx.xx.xx.xxx:6443" } ] }
and I am able to hit the pod from the minion:
ubuntu@ip-xxx-xx-xx-xxx:~$ curl http://10.103.61.173 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/">nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/">nginx.com</a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html>
I have tried re-creating the cluster several times, starting from scratch and I am stuck at this point.
Thanks.
-Jonathan
Comments
-
I am having the same issue
1 -
@jtronson
If you curl from master node any of the endpoints (instead of the ClusterIP), or from the minion to endpoints, what responses do you get?
I am assuming both master and minion are in the same SG?
Regardless where your pod is running (master or minion), curling the ClusterIP should produce the same result, since the service should be equally accessible from both nodes inside your cluster.
Have you tried opening the SG to all traffic, rather than individual ports?
Regards,
-Chris0 -
OK. Opening up the SG to "All Traffic" fixed the issue. So now I am just wondering what ports I was missing in the rule. Currently I have the following tcp ports opened:
22: ssh
80: http
443, 8443: https
5000: Registry
6443: K8s API Server
6666: Etcd
30000 - 32767: nodePorts
53 (UDP): kube dns
All ICMPThank you for the suggestion. At least now I can continue with the lesson!
-Jonathan
0 -
The list below seems to be incomplete, but a good start:
https://kubernetes.io/docs/setup/independent/install-kubeadm/And then there is this discussion:
https://stackoverflow.com/questions/39293441/needed-ports-for-kubernetes-cluster1 -
Hi @TITYKOUKI ,
If your master cannot reach the minion, you may be experiencing node-to-node networking issues. Try opening your SG to all ports, protocols, from all sources, so it does not restrict any other traffic. Another option would be to look at your VPC setup, if there is one.
Regards,
-Chris0 -
Hello,
If you would like to find a list of the ports in you you may consider adding a log line to the iptables on both nodes. As with other parts of Kubernetes there is much change going on, and the documentation on _kubernetes.io _tends to lag behind and/or not be accurate. You can put a log action on both the output as well as in the input chains, and from that get an understanding of what that particular version of Kubernetes wants to use for ports.
Regards,
0 -
@serewicz said:
Hello,If you would like to find a list of the ports in you you may consider adding a log line to the iptables on both nodes. As with other parts of Kubernetes there is much change going on, and the documentation on _kubernetes.io _tends to lag behind and/or not be accurate. You can put a log action on both the output as well as in the input chains, and from that get an understanding of what that particular version of Kubernetes wants to use for ports.
Regards,
Hi @serewicz, could you please provide a bash snippet to "adding a log line to the iptables on both nodes" and how to use the log for troubleshooting?
I read some iptables documentation but it does not seems so easy for a network newbie
Thanks a lot0 -
To make the log statement the first rule applied to inboudn traffic you can use this command: iptables -I INPUT -j LOG --log-prefix "K8s test " --log-level 1 or if trying to log outboud you could add the rule last to see what has made it that far with this command: iptables -A OUTPUT -j LOG --log-prefix "k8s-outbound " --log-level 1
0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 734 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 166 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 132 Cloud Native Developer IT Professional Program
- 122 Express Training Courses
- 122 Express Courses - Discussion Forum
- 5.9K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 222 LFD103 Class Forum
- 17 LFD110 Class Forum
- 34 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 3 LFD237 Class Forum
- 23 LFD254 Class Forum
- 689 LFD259 Class Forum
- 110 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 112 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 3 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 17 LFS158 Class Forum
- 5 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 118 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 50 LFS241 Class Forum
- 44 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 45 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 146 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 116 LFS260 Class Forum
- 156 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 8 LFW111 Class Forum
- 257 LFW211 Class Forum
- 180 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- SKF201 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 754 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 351 Ubuntu
- 465 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 366 Off Topic
- 114 Introductions
- 171 Small Talk
- 20 Study Material
- 534 Programming and Development
- 293 Kernel Development
- 223 Software Development
- 1.2K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 312 Installation
- 79 All In Program
- 79 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)