search

mbaykara / k8s-cluster

Kubernetes cluster with I control and II workers
MIT License
33 stars 47 forks source link

Quick question: connection refused second node #2

Closed vsoch closed 2 years ago

vsoch commented 2 years ago

hey @mbaykara ! I have some experience deploying apps, but am relatively new to admin k8s. I have one external server and decided VMs (Vagrant) would be a good avenue - and that's how I stumbled on your post! Everything is going smoothly so far - I have my main node running and one worker registered, but for the second worker:

I0109 04:02:10.761062    2208 token.go:217] [discovery] Failed to request cluster-info, will try again: Get "https://192.168.33.13:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp 192.168.33.13:6443: connect: connection refused

(That's produced by adding --v=5 - it seems to retry many times and then fail). One thing I didn't do following your tutorial are the steps after you do a health check, as I found my main to have all records of healthy, but I'm wondering if that step was important anyway, or perhaps there is another oversight I'm making.

Anyway - I think I am close! I'm really excited to have this up and running. Thanks for your help!

vsoch commented 2 years ago

Ah so I fixed this! I had renamed master -> main but of course missed one reference in the script to prepare the cluster, so (womp womp) it didn't know about main. My second node just registered successfully - sorry for the noise!