Lab 3.5 Who is providing IPs

When reading step 18 it seems to state calico is providing the cluster IP and pod ips are being provided by kubelet/kube proxy
Step18
"Verify the service configuration. First look at the service, then the endpoint information. Note the ClusterIP is not the
current endpoint. Calico provides the ClusterIP. The Endpoint is provided by kubelet and kube-proxy. Take note
of the current endpoint IP. In the example below it is 192.168.1.5:80. We will use this information in a few steps"
However based on what i see, it seems to be be that calico is control of assigning ip of pods
When i look at the nodes, i will see that the subnets being defined are actually different than what is being assigned to pods. You will also see that the pods running have annotations for calico.
student@master:~$ kubectl describe nodes | grep 192.168
projectcalico.org/IPv4IPIPTunnelAddr: 192.168.219.64
PodCIDR: 192.168.0.0/24
PodCIDRs: 192.168.0.0/24
projectcalico.org/IPv4IPIPTunnelAddr: 192.168.171.64
PodCIDR: 192.168.1.0/24
PodCIDRs: 192.168.1.0/24
student@master:~$ kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-d46f5678b-rbzrr 1/1 Running 0 9m1s 192.168.219.68 master
nginx-d46f5678b-w7k52 1/1 Running 0 31m 192.168.171.67 worker
nginx-d46f5678b-xkmmj 1/1 Running 0 9m1s 192.168.171.68 worker
student@master:~$
student@master:~$ kubectl describe pods | egrep "node|192"
Annotations: cni.projectcalico.org/podIP: 192.168.219.69/32
cni.projectcalico.org/podIPs: 192.168.219.69/32
IP: 192.168.219.69
IP: 192.168.219.69
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Annotations: cni.projectcalico.org/podIP: 192.168.171.67/32
cni.projectcalico.org/podIPs: 192.168.171.67/32
IP: 192.168.171.67
IP: 192.168.171.67
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Annotations: cni.projectcalico.org/podIP: 192.168.171.68/32
cni.projectcalico.org/podIPs: 192.168.171.68/32
IP: 192.168.171.68
IP: 192.168.171.68
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Looking for clarification to confirm that Calico is providing pods ip and cluster ips.
Comments
-
Its seem that I probably mistook the meaning behind the step18 . But interested in finding out where the pod subnets on each node is being defined and who is allocating the ip
0 -
Examining pod annotations and listing running pods in the cluster with the
-o wide
output flag reveal the pod IP addresses assigned by and managed by the network plugin from the default pod network192.168.0.0/16
.Regards,
-Chris0 -
Hello,
The network plugin, Calico, works with the kubeadm init default values, unless other values are passed during cluster initialization. As a result the IP pools are a mixture of two places, configured when the cluster is initialized.
Regards,
0 -
Thanks for Info!
0
Categories
- All Categories
- 51 LFX Mentorship
- 104 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 157 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 235 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 903 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 61 All In Program
- 61 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)