The cluster-info ConfigMap does not yet contain a JWS signature for token ID

1 개요

The cluster-info ConfigMap does not yet contain a JWS signature for token ID

# kubeadm join vcluster.example.com:443 --token to2kpd.yox075m9x8lvvoxr --discovery-token-ca-cert-hash sha256:cfba3ff3ba297183724c411c5a2548caeb01b194aaee3ac747e1468b858c275e -v=9
I0225 02:37:11.131070 1864629 join.go:412] [preflight] found NodeName empty; using OS hostname as NodeName
I0225 02:37:11.133505 1864629 initconfiguration.go:117] detected and using CRI socket: unix:///var/run/containerd/containerd.sock
[preflight] Running pre-flight checks
I0225 02:37:11.133941 1864629 preflight.go:93] [preflight] Running general checks
I0225 02:37:11.134203 1864629 checks.go:280] validating the existence of file /etc/kubernetes/kubelet.conf
I0225 02:37:11.134335 1864629 checks.go:280] validating the existence of file /etc/kubernetes/bootstrap-kubelet.conf
I0225 02:37:11.134425 1864629 checks.go:104] validating the container runtime
I0225 02:37:11.185940 1864629 checks.go:639] validating whether swap is enabled or not
I0225 02:37:11.186256 1864629 checks.go:370] validating the presence of executable crictl
...
I0225 02:36:08.974087 1864380 token.go:223] [discovery] The cluster-info ConfigMap does not yet contain a JWS signature for token ID "to2kpd", will try again
could not find a JWS signature in the cluster-info ConfigMap for token ID "to2kpd"

2 같이 보기

3 참고

https://discuss.kubernetes.io/t/cluster-info-configmap-does-not-yet-contain-a-jws-signature/14985