Lab number : Networking Weave Here is the question( Image 1) to find POD IP rang . . .

Kubernetes
#1

Nitin Garg:
Lab number : Networking Weave
Here is the question( Image 1) to find POD IP range configured by weave

I checked the inet range in weave network interface which is 10.46.0.0/12
Then I checked the --ipalloc-range in the weave process which is 10.32.0.0/12
Then I checked the ip address of pod which is 10.38.0.1 and does not belong to either of ranges then which one to believe because the option 10.X.X.X is irrelevant

image.png
image.png875×211 9.06 KB

image.png

#2

Nitin Garg:
Hey @Basavraj Nilkanthe @Mohamed Ayman could you please clarify this doubt. You two seem one of the most knowledgeable persons here

#3

Basavraj Nilkanthe:
@Nitin Garg . It seems they are asking you to identify pod IP range configured for CNI plugin weave… IP address of Nginx pod has nothing do with theis scenario… It won’t fall under weave network ip range… Simplest way to verify this check pod name of weave deployment and it’s corresponding ip address to confirm on that… To check it run kubectl get pods -A

#4

Basavraj Nilkanthe:
Otherwise describe deployment pod template of weave and check command or argument section to confirm what range they have configured

#5

Nitin Garg:
Dear @Basavraj Nilkanthe thank you for your response. Actually Weave pods are part of daemonset and belong to an altogether different IP range as I have asked in my other https://kodekloud.slack.com/archives/CHMV3P9NV/p1619260162164800|question. My concern is what decides the IP range allocated to the general PODS on every node. although @Mumshad Mannambeth did explained it clearly but the results are not matching with that.

#6

Basavraj Nilkanthe:
@Nitin Garg in cloud provider you get that easily and could you please check kube-apiserver and describe it. Or check kubelet service

#7

Basavraj Nilkanthe:
I am sure you must be getting either of them

#8

Basavraj Nilkanthe:
I am not around my personal laptop… I could have checked it.

#9

Basavraj Nilkanthe:
Hiya

#10

Basavraj Nilkanthe:
@Nitin Garg sorry, I found that, its niether associated with kube-apiserver or kubelet service

#11

Basavraj Nilkanthe:
This is something you can confirm when you are doing kubernetes setup from kubeadm

#12

Basavraj Nilkanthe:
you can find that information

#13

Nitin Garg:
Thanks for the details Basav … I will check myself

#14

Nitin Garg:
I appreciate your concern

#15

Basavraj Nilkanthe:

kubeadm init --apiserver-advertise-address=<ip-address-of-kmaster-vm> --pod-network-cidr=192.168.0.0/16
#16

Basavraj Nilkanthe:
This command we run on master node

#17

Basavraj Nilkanthe:
and second command we run on worker node to join master node

#18

Basavraj Nilkanthe:

sudo kubeadm join --apiserver-advertise-address=<ip-address-of-the master> --pod-network-cidr=192.168.0.0/16
#19

Basavraj Nilkanthe:
if you are describe or check kubeadm process running on your node

#20

Basavraj Nilkanthe:
you can get pod network range