Yes please.

The cloud-init installation comes after the step on your screenshot.

Are the 3 nodes VMs started? Can you post the output of sudo cat /var/log/messages?

I'd say any error in the console during the cloud-init installation.

Hi,

Nothing useful. Maybe you can try to delete the VMs and redeploy the cluster.

Thank you, I'll take a look tomorrow.

Is it the whole output for the master?

You can do that but it won't help us to understand what when wrong during the installation of the worker nodes 1 and 3.

Can you show me what's the output of sudo cat /var/log/messages for each nodes (master and workers)?

Concerning the CIDR, we are now using flannel as Container Network Interface, which uses a default CIDR (10.244.0.0/16) allocated to the pods network.

Thank you.

Are all VMs started?

What's the output of kubectl get pods --all-namespaces?

Yes, you should have something like that:

debian@master:~$ kubectl get nodes
NAME     STATUS   ROLES           AGE     VERSION
master   Ready    control-plane   6m52s   v1.26.3
node-1   Ready    <none>          115s    v1.26.3
node-2   Ready    <none>          2m47s   v1.26.3
node-3   Ready    <none>          2m36s   v1.26.3

Are all worker nodes vm started? What's the output of kubectl get events?

@fred974 said in Kubernetes cluster recipes not seeing nodes:

Should it be debian?

No, only the /home/debian/.kube/config is meant to be owned by debian user.

Are you using kubectl with debian user or with the root user?

It's hard to say without knowing what went wrong during the installation.

First, I would say to check if the config file /home/debian/.kube/config is the same as /etc/kubernetes/admin.conf and if debian is correctly assign as the owner of the file.