Lab 3.4 - Lab 9.1 Control plane can't reach worker's pod
Hello, I'm trying to follow all the LAB with success but I have 2 issue in Lab 3.4: Deploy A Simple Application and in Lab 9.1: Services.
Basically from the control plane (10.0.1.5) I cannot reach pod network (192.168.0.0/16) in the worker node (10.0.1.4).
The cluster is in ready state and the pods are all running.
This is the output from LAB 3.1:
azureadm@k8scp:~$ kubectl get svc,ep -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service/kubernetes ClusterIP 10.96.0.1 443/TCP 19h
service/nginx ClusterIP 10.100.75.41 80/TCP 7h38m app=nginx
NAME ENDPOINTS AGE
endpoints/kubernetes 10.0.1.5:6443 19h
endpoints/nginx 192.168.103.210:80 7h38m
azureadm@k8scp:~$
I cannot curl 192.168.103.210:80 without getting a timeout.
curling from worker node succeed.
Thanks
Comments
-
I have the same problem
0 -
Hi @fabio.sasso,
Are you by any chance running your cluster on Azure cloud infrastructure?
Regards,
-Chris1 -
Hi @sirgabriel,
Please provide some descriptive details about your infrastructure and cluster, so we can understand the "problem".
Regards,
-Chris0 -
@chrispokorni said:
Hi @fabio.sasso,Are you by any chance running your cluster on Azure cloud infrastructure?
Regards,
-ChrisHello Chris,
Exactly I'm on Azure. from NSG side it seems all ok.
Please let me know what I can check.Thanks a lot!
0 -
Hi @fabio.sasso,
Azure is known to require additional and very specific configuration options for the network plugins to work with Azure's own networking implementation. However, that is not needed by the recommended cloud infrastructure providers - AWS and GCP, nor the local solutions with hypervisors such as VirtualBox, KVM, or VMware.
While we do not support the lab exercises on the Azure infrastructure, there are a few forum posts from learners who attempted to run them on Azure, with lessons learned and networking configuration tips.
Regards,
-Chris0 -
@chrispokorni As it happens, I am running my cluster on AWS but I am finding that as @fabio.sasso reports I cannot get the curl commands of Lab 9.1 step 12 to work from the control plane node of my cluster, but it works from the worker node just fine. The nodes are built using Ubuntu 20.04.
0 -
I have exactly the same problem, however, my lab environment comprises three VirtualBoxVMs and Cilium on a Ubuntu 22.04 host.
Regards
0 -
Hi @jmfwss,
To correctly configure the networking for your VMs, on VirtualBox please ensure you enable promiscuous mode to allow all inbound traffic, and use the recommended guest OS - Ubuntu 20.04 LTS.
Regards,
-Chris0 -
I have promiscuous mode enabled and my guest OSs are all Ubuntu 20.04 LTS. However, I cannot reach the pods running on the cluster network. Currently, I have Pods running in three Networks:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES accounting nginx-one-5bdc6ddf4b-cvr46 1/1 Running 1 (3h26m ago) 23h 192.168.1.223 worker1 <none> <none> accounting nginx-one-5bdc6ddf4b-ft2vd 1/1 Running 1 (3h26m ago) 23h 192.168.1.122 worker1 <none> <none> default nfs-subdir-external-provisioner-86bcbb46d7-xjknw 1/1 Running 2 (3h26m ago) 2d1h 192.168.1.238 worker1 <none> <none> kube-system cilium-operator-788c7d7585-8mdzg 1/1 Running 8 (3h26m ago) 125d 10.10.10.21 worker1 <none> <none> kube-system cilium-operator-788c7d7585-p86rv 1/1 Running 9 (3h26m ago) 125d 10.0.2.15 cp <none> <none> kube-system cilium-qk8pn 1/1 Running 9 (3h26m ago) 140d 10.0.2.15 cp <none> <none> kube-system cilium-sdsfv 1/1 Running 10 (3h25m ago) 137d 10.10.10.22 worker2 <none> <none> kube-system cilium-wxdml 1/1 Running 8 (3h26m ago) 140d 10.10.10.21 worker1 <none> <none> kube-system coredns-5d78c9869d-7mxs4 1/1 Running 8 (3h26m ago) 125d 192.168.1.40 worker1 <none> <none> kube-system coredns-5d78c9869d-zr7rj 1/1 Running 9 (3h26m ago) 125d 192.168.0.80 cp <none> <none> kube-system etcd-cp 1/1 Running 10 (3h26m ago) 125d 10.0.2.15 cp <none> <none> kube-system kube-apiserver-cp 1/1 Running 10 (3h26m ago) 125d 10.0.2.15 cp <none> <none> kube-system kube-controller-manager-cp 1/1 Running 10 (3h26m ago) 125d 10.0.2.15 cp <none> <none> kube-system kube-proxy-76jpk 1/1 Running 9 (3h26m ago) 125d 10.0.2.15 cp <none> <none> kube-system kube-proxy-h9fll 1/1 Running 8 (3h26m ago) 125d 10.10.10.21 worker1 <none> <none> kube-system kube-proxy-pqqm7 1/1 Running 10 (3h25m ago) 125d 10.10.10.22 worker2 <none> <none> kube-system kube-scheduler-cp 1/1 Running 10 (3h26m ago) 125d 10.0.2.15 cp <none> <none> low-usage-limit limited-hog-66d5cd76bc-q6rmz 1/1 Running 10 (3h25m ago) 116d 192.168.2.226 worker2 <none> <none>
10.0.2.15 is the standard address assigned to the VM by Virtualbox, 10.10.10.* is the network range I assigned to the VMS in the Vagrantfile, 192.168.. is the cluster CIDR as specified in spec.containers.command[] (
--cluster-cidr=192.168.0.0/16
) of /etc/kubernetes/manifests/kube-controller-manager.yaml and in data.cluster-pool-ipv4-cidr of the Cilium config map.Regards
Jens0 -
Hi @jmfwss,
There are two host networks that are inconsistently picked by the Kubernetes components and plugins. That is why the routing is not behaving as expected.
Eliminate one of the node networks, keeping a single bridged network interface per VirtualBox VM with a DHCP server configured on any private subnet (because Cilium supports multiple overlapping network subnets, as opposed to other network plugins). For clarity, however, a node network of 10.200.0.0/16 or smaller may help to understand how Kubernetes and its plugins' IP addresses are utilized.Regards,
-Chris0 -
Hi Chris,
thanks for your help. After digging into the network configuration, some googling, and reanalyzing my setup, I found the cause for my problem: a missing double quote in /etc/systemd/system/kubelet.service.d/10-kubeadm.conf where I set the value of environment variableKUBELET_EXTRA_ARGS
to--node-ip=10.10.10.11
. m(Regards,
Jens0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 735 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 167 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
- 221 LFD103 Class Forum
- 17 LFD110 Class Forum
- 33 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
- 109 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 109 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
- 13 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
- 116 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 49 LFS241 Class Forum
- 43 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
- 145 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
- 154 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
- 7 LFW111 Class Forum
- 257 LFW211 Class Forum
- 178 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 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.1K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 311 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)