Question: Do we need to remember the whole path when installing weave/ flannel a . . .

Kubernetes-Slack Discussions
#1

R Banerjee:
Question: Do we need to remember the whole path when installing weave/ flannel as the CNI with kubeadm?

#2

todoriri:
you have the path to weave in the docs
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/

#3

R Banerjee:
aah, ok… but if we are asked to install flannel ( I am not sure if we would be or not)

#4

todoriri:
They shouldn’t ask to install any specific CNI plugin, unless they provide also the path in the question, I believe

#5

todoriri:
when is your exam?

#6

R Banerjee:
very very soon :stuck_out_tongue:

#7

R Banerjee:
Next week …

#8

Sameer Jain:
https://kubernetes.io/fr/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network

#9

Sameer Jain:
here all the networking path if you change language

#10

R Banerjee:
@Sameer Jain thanks :smile: Why do they keep different versions for the same docs ? :smile:

#11

todoriri:
Thanks for the URL Sameer!

#12

Sameer Jain:
just make sure that for weave --pod-network-cidr=10.32.0.0/12

#13

Sameer Jain:
while for flannel command is outdated replace

a70459be0084506e4ec919aa1c114638878db11b

with master and default cidr block is --pod-network-cidr = 10.244.0.0/16

#14

R Banerjee:
Right now, I am restarting the lab for kubeadm… I seemed to have installed it incorrectly twice ( or maybe the answer is not working correctly)

#15

unnivkn:
https://kodekloud.slack.com/archives/CHMV3P9NV/p1629867656144200

#16

R Banerjee:
~While running the lab for setting up kubeadm, I just ran apt-get flannel and the kubeadm installation worked… that was a bit weird~ :slightly_smiling_face:

~Weird bcz I didn’t have to configure flannel~

Seems kubelet doesn’t work, getting error during kubeadm init

#17

R Banerjee:
he HTTP call equal to ‘curl -sSL http://localhost:10248/healthz’ failed with error: Get “http://localhost:10248/healthz”: dial tcp 127.0.0.1:10248: connect: connection refused.

Kubelet fails to start… if this happens in the main exam, how to recover ?

#18

Sameer Jain:
what was kubeadm init command used?

#19

todoriri:
check the cgroup drivers on kubelet and docker, they must use the same driver
https://kodekloud.slack.com/archives/CHMV3P9NV/p1629204957296100?thread_ts=1629202490.295400&cid=CHMV3P9NV

#20

R Banerjee:
Sorry, I went out after temporarily giving up :smile:
I will check the exec-opts, I feel @todoriri is right :slightly_smiling_face: Ididnt check the cgroup but it mightbe probablytheone… will test it out in a few hours