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
Basavraj Nilkanthe:
I am sure you must be getting either of them
Basavraj Nilkanthe:
I am not around my personal laptop… I could have checked it.
Basavraj Nilkanthe:
Hiya
Basavraj Nilkanthe:
@Nitin Garg sorry, I found that, its niether associated with kube-apiserver or kubelet service
Basavraj Nilkanthe:
This is something you can confirm when you are doing kubernetes setup from kubeadm
Basavraj Nilkanthe:
you can find that information
Nitin Garg:
Thanks for the details Basav … I will check myself
Nitin Garg:
I appreciate your concern
Basavraj Nilkanthe:
kubeadm init --apiserver-advertise-address=<ip-address-of-kmaster-vm> --pod-network-cidr=192.168.0.0/16
Basavraj Nilkanthe:
This command we run on master node
Basavraj Nilkanthe:
and second command we run on worker node to join master node
Basavraj Nilkanthe:
sudo kubeadm join --apiserver-advertise-address=<ip-address-of-the master> --pod-network-cidr=192.168.0.0/16
Basavraj Nilkanthe:
if you are describe or check kubeadm process running on your node
Basavraj Nilkanthe:
you can get pod network range
Nitin Garg:
Actually mumshad explained in one of the lectures that POD IP range allocation is related to network addon … that is weave plugin so I was more concerned than that why it is not matching with either INET range in the weave network interface or with IP alloc range of weave plugin
Basavraj Nilkanthe:
I dont think this CNI plugin has that information
Basavraj Nilkanthe:
it is enabling networking stuff for your pods
Basavraj Nilkanthe:
I checked on calico network plugin
Basavraj Nilkanthe:
no where pod network cidr range configured