Can you ping 10.8.0.1 from the worker? If not, your openVPN is probably down and i would check the logs for that service on the box.
yes I can, From master node I can ping to Worker node and vice-versa! I see that the API server are bind to :::6443 port of the master node, is that the cause of this problem
Shouldn't be. Add -v to your kubeadm command and see what its doing.
Here is the log I got when run "kubeadm join ..." command,
Failed to request cluster info, will try again: [Get 10.8.0.1:6443/api/v1/namespaces/ku... dial tcp 10.8.0.1:6443: i/o timeout]
but I'm still able to ping 10.8.0.1 from the worker node
Can you access that URL in your browser on either the worker or the control plane node?
yes, I'm able to get response when execute the curl command to that URL on master node
Do we need to tell kubeadm to use "tun0" network interface instead of default one?
It sounds like you have a firewall blocking that port then
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Can you ping 10.8.0.1 from the worker? If not, your openVPN is probably down and i would check the logs for that service on the box.
yes I can, From master node I can ping to Worker node and vice-versa! I see that the API server are bind to :::6443 port of the master node, is that the cause of this problem
Shouldn't be. Add -v to your kubeadm command and see what its doing.
Here is the log I got when run "kubeadm join ..." command,
Failed to request cluster info, will try again: [Get 10.8.0.1:6443/api/v1/namespaces/ku... dial tcp 10.8.0.1:6443: i/o timeout]
but I'm still able to ping 10.8.0.1 from the worker node
Can you access that URL in your browser on either the worker or the control plane node?
yes, I'm able to get response when execute the curl command to that URL on master node
Do we need to tell kubeadm to use "tun0" network interface instead of default one?
It sounds like you have a firewall blocking that port then