Can't seem to properly create a K8S cluster
I am following what is at
The master is being created, but none of the nodes are getting created.
Is Private LAN the choice one should use? When I didn't use it the nodes were created but the networking didn't work. If I use Private LAN, the nodes don't get created at all.
Looking for any and all help.
When I use eth0 the cluster is created but doesn't work properly.
debian@master:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-66bff467f8-ksl9p 0/1 Pending 0 171m kube-system coredns-66bff467f8-lxbr4 0/1 Pending 0 171m kube-system etcd-master 1/1 Running 0 171m kube-system kube-apiserver-master 1/1 Running 0 171m kube-system kube-controller-manager-master 1/1 Running 0 171m kube-system kube-proxy-27cnt 1/1 Running 0 171m kube-system kube-proxy-54472 1/1 Running 0 165m kube-system kube-proxy-pg2p6 1/1 Running 0 167m kube-system kube-router-hzv6j 0/1 CrashLoopBackOff 36 165m kube-system kube-router-lvhsl 0/1 CrashLoopBackOff 37 167m kube-system kube-router-mmb9p 1/1 Running 0 171m kube-system kube-scheduler-master 1/1 Running 0 171m debian@master:~$
you don't have to use Private LAN, the photo is an example in our homelab where I used a network called that way. the only requirement is taht there's a DHCP running in the network so that the master can get an IP for the nodes to use.
Can you elaborate 'doesn't work properly'? How many nodes did you create? Is the issue the
The network CIDR you entered in the recipe should be different than the address range of the network on which the VMs runs.
@BenjiReis said in Can't seem to properly create a K8S cluster:
the only requirement is taht there's a DHCP running in the network so that the master can get an IP for the nodes to use.
That is almost certainly the problem here.
So, I am thinking using a VLAN and running a VM (like pfsense) to provide DHCP.
How does that sound?
Yes that should work