Hey there , need you help using kubeadm Im trying to implemnt what we learned a . . .

Kubernetes-Slack Discussions
#1

Eyal Solomon:
Hey there , need you help using kubeadm

Im trying to implemnt what we learned and configure a cluster by my own in AWS

I usuing deafult VPC (172.31.0.0/16)
( created SG with all ports open on 172.31.0.0/16 - VPC cider block)

I have a question when usuing kubeadm init

kubeadm init --apiserver-advertise-address=<master_instance_ip> --pod-network-cidr=172.31.0.0/16  --ignore-preflight-errors=all

So now it means i can deploy weave-net like this right ?

kubectl apply -f "<https://cloud.weave.works/k8s/net?k8s-version=$(kubectl> version | base64 | tr -d '\n')&amp;env.IPALLOC_RANGE=172.31.0.0/16"

cluster-ip-range = 172.31.0.0/16
pod-ip-range=172.31.0.0/16
service-ip-range=?

What else do i need to configure so it works properly ?

THANKS !!
@Tej_Singh_Rana @unnivkn

#2

Tej_Singh_Rana:
Hello, @Eyal Solomon
You can try without &amp;env.IPALLOC_RANGE=172.31.0.0/16 and it should work because weave by default use 10.32.0.0/12

#3

Eyal Solomon:
thanks ! i actually remember from the great lesson
vpc ip range is 172.31.0.0/16
wouldnt be out of the vpc range ?

#4

unnivkn:

image.png
image.png1203×659 46.9 KB

#5

Eyal Solomon:
thank both of you for the response

but i still cant understand if my VPC ip range is
172.31.0.0/16

how could my service-ip range be
10.96.0.0/12

shouldnt it be inside the VPC ip range ?
@unnivkn @Tej_Singh_Rana

#6

unnivkn:
usually we are not setting service-range ip & PodCIDR while installing k8s rt? Once you give cluster-cidr, service-ip-range will take automatically i believe. PodCIDR may take once you install network-plugin. Is there anywhere in EKS, mandatory ask for service-ip range & PodCIDR ?

#7

unnivkn:
just try weavenet install & see what ip range its generating

#8

Eyal Solomon:
Im trying to implement this with 2 ubuntu 20.04 vm’s
as you can see
cluster cider - 172.31.1.0/24 ( in VPC range )
service ip-range = 10.96.0.0/12 ( OUTSIDE of vpc range )

this is what im having trouble understanding

Screen Shot 2021-09-27 at 17.48.55.png
Screen Shot 2021-09-27 at 17.48.55.png1163×434 75 KB

#9

unnivkn:
can you create a deployment/pod & svc & see what ip it is creating?

#10

unnivkn:
k run test-pod --image=nginx --port=80 --expose
k get po,svc,ep -o wide

#11

Eyal Solomon:
you see ?
services range is different than cluster ip range as i configured it
also this ip range 10.96.0.0/16 is NOT inside my VPC range
thats so weird :sweat_smile:

Screen Shot 2021-09-27 at 19.12.52.png
Screen Shot 2021-09-27 at 19.12.52.png1297×289 21.7 KB

#12

unnivkn:

image.png
image.png848×838 451 KB

#13

unnivkn:
@Eyal Solomon please try this. hope this work for you