Error adding windows node to K8s cluster

General Discussions Windows
1

Hi Folks,
I’m having trouble joining the windows node to the cluster.
I’m getting this error:

kubeadm join 192.168.x.x:6443 --token skuxj9.hjv53yrzy9m8j3rt     --discovery-token-ca-cert-hash sha256:3f5f0c
9d2aca0b40fa903ddc3ad12004f276455dd50991abf8ecf5e95337dc8a
W0428 13:07:02.415590   26212 join.go:346] [preflight] WARNING: JoinControlPane.controlPlane settings will be ignored whe
n control-plane flag is not set.
[preflight] Running pre-flight checks
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 19.03.5. Latest valid
ated version: 19.03
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
W0428 13:07:07.648270   26212 utils.go:26] The recommended value for "clusterDNS" in "KubeletConfiguration" is: [10.233.0
espace
[kubelet-start] Writing kubelet configuration to file "\\var\\lib\\kubelet\\config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "\\var\\lib\\kubelet\\kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost
:10248/healthz: dial tcp [::1]:10248: connectex: No connection could be made because the target machine actively refused
it..
:10248/healthz: dial tcp [::1]:10248: connectex: No connection could be made because the target machine actively refused
it..
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost
:10248/healthz: dial tcp [::1]:10248: connectex: No connection could be made because the target machine actively refused
it..
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost
:10248/healthz: dial tcp [::1]:10248: connectex: No connection could be made because the target machine actively refused
it..

Unfortunately, an error has occurred:
        timed out waiting for the condition

This error is likely caused by:

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
        - 'systemctl status kubelet'
        - 'journalctl -xeu kubelet'
error execution phase kubelet-start: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher
PS C:\k>

I’m using 1.18.0 release. I followed this link for the instructions, but no luck.
Seriously, what is wrong with it? :man_facepalming: :man_facepalming: :man_facepalming:

2

do you have the kubelet docker running on the windows node

docker ps

See if kubelet is there. otherwise it may not be responding. That looks to be the reason the healthz is failing.

3

Yes, the kubelet is running as well as the docker.
any ideas?
Have you done it with no issues?

4

I have a windows node running in azure as part of my kubernetes cluster. I didn’t have to do any firewall stuff with it, but aks spun it up in an optimal state. You could try temp disabling the firewall (if it’s behind a main firewall) and see if that works. That would probably be my next step.

5

Hello, I’ve been experiencing same issue, any solution for this?