You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kubeadm join 192.168.200.160:6443 --token 7nv61h.9jtc4jma273dd1u0 --discovery-token-ca-cert-hash sha256:90e036fb228057cfbc5b338609c292f549ade0d3ec547c5704606a9dade8a2c6
i use kubeadm join a work node to master, it failed
issue log:
x509 certficate is valid 192.11.90.160, 127.0.0.1 not 192.168.200.160
then i change 192.168.200.160 to domain, try it, it failed Get "https://xxxx:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s":
net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
What you expected to happen?
how to fix it
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
The text was updated successfully, but these errors were encountered:
The apiserver is bound to 192.11.90.160, and is 192.168.200.160 another IP of the master node?
Can the apiserver bind the 192.168.200.160 as well in kubeadm init --apiserver-advertise-address=192.168.200.160?
You seem to have troubles using Kubernetes and kubeadm.
Note that our issue trackers should not be used for providing support to users.
There are special channels for that purpose.
What keywords did you search in kubeadm issues before filing this one?
If you have found any duplicates, you should instead reply there and close this page.
If you have not found any duplicates, delete this section and continue on.
Is this a BUG REPORT or FEATURE REQUEST?
Choose one: BUG REPORT or FEATURE REQUEST
Versions
kubeadm version (use
kubeadm version
):Environment:
kubectl version
):uname -a
):What happened?
kubeadm join 192.168.200.160:6443 --token 7nv61h.9jtc4jma273dd1u0 --discovery-token-ca-cert-hash sha256:90e036fb228057cfbc5b338609c292f549ade0d3ec547c5704606a9dade8a2c6
i use kubeadm join a work node to master, it failed
issue log:
x509 certficate is valid 192.11.90.160, 127.0.0.1 not 192.168.200.160
then i change 192.168.200.160 to domain, try it, it failed Get "https://xxxx:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s":
net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
What you expected to happen?
how to fix it
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
The text was updated successfully, but these errors were encountered: