Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

I want to use kind to create a cluster, and no matter how I operate, I will get an error. #3460

Closed
1569099266 opened this issue Dec 22, 2023 · 15 comments
Closed

I want to use kind to create a cluster, and no matter how I operate, I will get an error. #3460

1569099266 opened this issue Dec 22, 2023 · 15 comments
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@1569099266
Copy link

root@master:# kind get cluster
ERROR: unknown command "cluster" for "kind get"
root@master:#
root@master:~# kind create cluster --config 1.yaml --name dev
Creating cluster "dev" ...
✓ Ensuring node image (kindest/node:v1.21.1) 🖼
✓ Preparing nodes 📦 📦 📦 📦 📦
✓ Configuring the external load balancer ⚖
✓ Writing configuration 📜
✗ Starting control-plane 🕹
ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged dev-control-plane kubeadm init --skip-phases=preflight --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1
Command Output: I1222 14:37:30.058821 184 initconfiguration.go:246] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
[init] Using Kubernetes version: v1.21.1
[certs] Using certificateDir folder "/etc/kubernetes/pki"
I1222 14:37:30.081390 184 certs.go:110] creating a new certificate authority for ca
[certs] Generating "ca" certificate and key
I1222 14:37:30.640553 184 certs.go:487] validating certificate period for ca certificate
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [dev-control-plane dev-external-load-balancer kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 172.18.0.6 127.0.0.1]
[certs] Generating "apiserver-kubelet-client" certificate and key
I1222 14:37:31.349295 184 certs.go:110] creating a new certificate authority for front-proxy-ca
[certs] Generating "front-proxy-ca" certificate and key
I1222 14:37:31.872870 184 certs.go:487] validating certificate period for front-proxy-ca certificate
[certs] Generating "front-proxy-client" certificate and key
I1222 14:37:32.117800 184 certs.go:110] creating a new certificate authority for etcd-ca
[certs] Generating "etcd/ca" certificate and key
I1222 14:37:33.091746 184 certs.go:487] validating certificate period for etcd/ca certificate
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [dev-control-plane localhost] and IPs [172.18.0.6 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [dev-control-plane localhost] and IPs [172.18.0.6 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
I1222 14:37:36.061464 184 certs.go:76] creating new public/private key files for signing service account users
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I1222 14:37:36.725061 184 kubeconfig.go:101] creating kubeconfig file for admin.conf
[kubeconfig] Writing "admin.conf" kubeconfig file
I1222 14:37:37.763474 184 kubeconfig.go:101] creating kubeconfig file for kubelet.conf
[kubeconfig] Writing "kubelet.conf" kubeconfig file
I1222 14:37:38.380208 184 kubeconfig.go:101] creating kubeconfig file for controller-manager.conf
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
I1222 14:37:38.691855 184 kubeconfig.go:101] creating kubeconfig file for scheduler.conf
[kubeconfig] Writing "scheduler.conf" kubeconfig file
I1222 14:37:40.011840 184 kubelet.go:63] Stopping the kubelet
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
I1222 14:37:40.320376 184 manifests.go:96] [control-plane] getting StaticPodSpecs
I1222 14:37:40.321409 184 certs.go:487] validating certificate period for CA certificate
I1222 14:37:40.321597 184 manifests.go:109] [control-plane] adding volume "ca-certs" for component "kube-apiserver"
I1222 14:37:40.321619 184 manifests.go:109] [control-plane] adding volume "etc-ca-certificates" for component "kube-apiserver"
I1222 14:37:40.321732 184 manifests.go:109] [control-plane] adding volume "k8s-certs" for component "kube-apiserver"
I1222 14:37:40.321759 184 manifests.go:109] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-apiserver"
I1222 14:37:40.321779 184 manifests.go:109] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-apiserver"
I1222 14:37:40.337785 184 manifests.go:126] [control-plane] wrote static Pod manifest for component "kube-apiserver" to "/etc/kubernetes/manifests/kube-apiserver.yaml"
I1222 14:37:40.337826 184 manifests.go:96] [control-plane] getting StaticPodSpecs
[control-plane] Creating static Pod manifest for "kube-controller-manager"
I1222 14:37:40.338572 184 manifests.go:109] [control-plane] adding volume "ca-certs" for component "kube-controller-manager"
I1222 14:37:40.338595 184 manifests.go:109] [control-plane] adding volume "etc-ca-certificates" for component "kube-controller-manager"
I1222 14:37:40.338604 184 manifests.go:109] [control-plane] adding volume "flexvolume-dir" for component "kube-controller-manager"
I1222 14:37:40.338613 184 manifests.go:109] [control-plane] adding volume "k8s-certs" for component "kube-controller-manager"
I1222 14:37:40.338621 184 manifests.go:109] [control-plane] adding volume "kubeconfig" for component "kube-controller-manager"
I1222 14:37:40.338630 184 manifests.go:109] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-controller-manager"
I1222 14:37:40.338639 184 manifests.go:109] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-controller-manager"
I1222 14:37:40.341513 184 manifests.go:126] [control-plane] wrote static Pod manifest for component "kube-controller-manager" to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
I1222 14:37:40.341724 184 manifests.go:96] [control-plane] getting StaticPodSpecs
[control-plane] Creating static Pod manifest for "kube-scheduler"
I1222 14:37:40.343362 184 manifests.go:109] [control-plane] adding volume "kubeconfig" for component "kube-scheduler"
I1222 14:37:40.345073 184 manifests.go:126] [control-plane] wrote static Pod manifest for component "kube-scheduler" to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I1222 14:37:40.347424 184 local.go:74] [etcd] wrote Static Pod manifest for a local etcd member to "/etc/kubernetes/manifests/etcd.yaml"
I1222 14:37:40.347451 184 waitcontrolplane.go:87] [wait-control-plane] Waiting for the API server to be healthy
I1222 14:37:40.349564 184 loader.go:372] Config loaded from file: /etc/kubernetes/admin.conf
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
I1222 14:37:40.353996 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:40.354116 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:41.356824 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:41.356926 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:42.359103 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:42.359183 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:43.361734 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:43.361858 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:44.363812 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:44.363888 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:45.366283 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:45.366397 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:46.369556 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:46.369667 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:47.372043 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:47.372120 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:48.373884 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:48.373964 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:49.376476 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:49.376560 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:50.879566 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:50.879671 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:51.881625 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:51.881695 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:52.884228 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:52.884338 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:53.886842 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:53.886957 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:54.889626 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:54.889704 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:55.892547 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:55.892657 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:56.895491 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:56.895573 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:57.897623 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:57.897744 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:58.900587 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:37:58.900679 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:37:59.904026 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:37:59.904182 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:01.379841 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:01.379948 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:02.382044 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:02.382124 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:03.385146 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:03.385227 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:04.388023 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:04.388123 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:05.390610 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:05.390690 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:06.392995 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:06.393072 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:07.395418 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:07.395494 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:08.397944 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:08.398024 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:09.400611 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:09.400690 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:10.403396 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:10.403512 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:11.879854 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:11.879968 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:12.882408 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:12.882484 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:13.884794 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:13.884904 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:14.887607 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:14.887721 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:15.889825 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:15.889897 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:16.891635 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:16.891706 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:17.894740 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:17.894838 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:18.898049 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:18.898166 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:19.900713 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:19.900825 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
[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: connect: connection refused.
I1222 14:38:20.903208 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:20.903294 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:22.378677 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:22.378746 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:23.381218 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:23.381336 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:24.383676 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:24.383780 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
[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: connect: connection refused.
I1222 14:38:25.386419 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:25.386497 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:26.388731 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:26.388812 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:27.391646 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:27.391743 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:28.394111 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:28.394193 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:29.396612 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:29.396721 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:30.400801 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:30.400935 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:31.403011 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:31.403142 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:32.879312 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:32.879379 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:33.881574 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:33.881654 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:34.884668 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:34.884766 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
[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: connect: connection refused.
I1222 14:38:35.887259 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:35.887364 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:36.889609 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:36.889694 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:37.892087 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:37.892190 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:38.894798 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:38.894897 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:39.897645 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:39.897727 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:40.899853 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:40.899925 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:41.903147 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:41.903236 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:43.379720 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:43.379796 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:44.382137 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:44.382216 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:45.384695 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:45.384775 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:46.386677 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:46.386773 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:47.389087 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:47.389166 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:48.391454 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:48.391541 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:49.394060 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:49.394155 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:50.397345 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:50.397426 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:51.400653 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:51.400769 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:52.403413 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:52.403523 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:53.879229 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:53.879314 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:54.881794 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:54.881943 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
[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: connect: connection refused.
I1222 14:38:55.885045 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:55.885145 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:56.888289 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:56.888422 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:57.890981 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:38:57.891092 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:58.893951 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:58.894028 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:38:59.897069 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:38:59.897184 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:00.900184 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:00.900285 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:01.902473 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:01.902559 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:02.905110 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:02.905193 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:04.379905 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:04.379990 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:05.383288 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:05.383400 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:06.386357 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:06.386521 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:07.389009 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:07.389077 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:08.395521 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 5 milliseconds
I1222 14:39:08.395620 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:09.398651 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:09.398735 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:10.400842 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:10.400903 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:11.403259 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:11.403350 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:12.405567 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:12.405644 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:13.408063 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:13.408256 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:14.878922 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:14.879001 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:15.881473 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:15.881581 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:16.883634 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:16.883718 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:17.886178 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:17.886252 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:18.888399 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:18.888479 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:19.890498 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:19.890576 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:20.892658 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:20.892728 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:21.894682 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:21.894794 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:22.897241 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:22.897373 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:23.899934 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:23.900012 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:25.379941 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:25.380031 184 request.go:959] Got a Retry-After 1s response for attempt 1 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:26.382569 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:26.382650 184 request.go:959] Got a Retry-After 1s response for attempt 2 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:27.385635 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:27.385750 184 request.go:959] Got a Retry-After 1s response for attempt 3 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:28.388537 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:28.388610 184 request.go:959] Got a Retry-After 1s response for attempt 4 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:29.391147 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:29.391232 184 request.go:959] Got a Retry-After 1s response for attempt 5 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:30.394115 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:30.394199 184 request.go:959] Got a Retry-After 1s response for attempt 6 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:31.396619 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:31.396694 184 request.go:959] Got a Retry-After 1s response for attempt 7 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:32.398921 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:32.399032 184 request.go:959] Got a Retry-After 1s response for attempt 8 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:33.401996 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 1 milliseconds
I1222 14:39:33.402075 184 request.go:959] Got a Retry-After 1s response for attempt 9 to https://dev-external-load-balancer:6443/healthz?timeout=10s
I1222 14:39:34.404510 184 round_trippers.go:454] GET https://dev-external-load-balancer:6443/healthz?timeout=10s in 2 milliseconds
I1222 14:39:34.404699 184 request.go:959] Got a Retry-After 1s response for attempt 10 to https://dev-external-load-balancer:6443/healthz?timeout=10s
[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: connect: connection refused.

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

This error is likely caused by:
	- The kubelet is not running
	- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

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'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.

Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
	- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
	Once you have found the failing container, you can inspect its logs with:
	- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock logs CONTAINERID'

couldn't initialize a Kubernetes cluster
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/init.runWaitControlPlanePhase
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/init/waitcontrolplane.go:114
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:234
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdInit.func1
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:152
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
/usr/local/go/src/runtime/proc.go:225
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1371
error execution phase wait-control-plane
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:235
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdInit.func1
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:152
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
/usr/local/go/src/runtime/proc.go:225
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1371
root@master:~#

image
image
image
@1569099266 1569099266 added the kind/bug Categorizes issue or PR as related to a bug. label Dec 22, 2023
@stmcginnis
Copy link
Contributor

Can you add the output from docker info? Paste the text, not a screenshot of the text please.

I was able to create a cluster using the same config file, so that makes me think this is something in your local environment. Note that creating a cluster with multiple nodes does have the risk of running into host resource issues with CPU, memory, inotify resources, and others. I would suggest starting with a smaller cluster to see if there is a point where you start having trouble.

Also make sure you don't have a lot of other containers running. Even stopped ones. It might be good to run docker system prune -a --volumes to make sure everything is cleaned up before trying to create a new cluster.

@BenTheElder
Copy link
Member

Can you please try with a minimal cluster first? The log output suggests you're using a custom multi-node config.

@bzsuni
Copy link
Contributor

bzsuni commented Dec 28, 2023

I encountered the same issue. I tried creating a cluster using a command like

kind create cluster --name kind-2

and it worked fine.
However, when using a configuration file, like

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: network-chart
networking:
  kubeProxyMode: iptables
  disableDefaultCNI: true
nodes:
  - role: control-plane
  - role: worker
  - role: worker

there is a problem.

@BenTheElder
Copy link
Member

Please check https://kind.sigs.k8s.io/docs/user/known-issues/

Common one for operating more nodes include e.g. running out of inotify limit on the host https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files

@achu911
Copy link

achu911 commented Jan 4, 2024

Please test multi nodes，I upgrade kind version, and I also get a same error。

@achu911
Copy link

achu911 commented Jan 4, 2024

[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: connect: connection refused.

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

This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

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'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all running Kubernetes containers by using crictl:
- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock logs CONTAINERID'
couldn't initialize a Kubernetes cluster
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/init.runWaitControlPlanePhase
cmd/kubeadm/app/cmd/phases/init/waitcontrolplane.go:108
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
cmd/kubeadm/app/cmd/phases/workflow/runner.go:259
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
cmd/kubeadm/app/cmd/phases/workflow/runner.go:446
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
cmd/kubeadm/app/cmd/phases/workflow/runner.go:232
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdInit.func1

@domoran
Copy link

domoran commented Jan 8, 2024

I have the same problem with the newest version of kind. It worked exactly once to create a cluster using "kind create cluster". Now afterwards every attempt fails with the above error. Restarting the docker service did not work. A reboot fixed the problem.

@liangyuanpeng
Copy link
Contributor

@bzsuni @domoran @achu911

Please provide more info here, OS/docker version/kind version/kubelet error log/command of kind create cluster/ kind config file , etc...

@liangyuanpeng
Copy link
Contributor

/remove-kind bug
/kind support

I think this is a support first. If the problem becomes clear and it is confirmed to be a bug, we can go back to the bug.

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. and removed kind/bug Categorizes issue or PR as related to a bug. labels Jan 10, 2024
@tao12345666333
Copy link
Member

tao12345666333 commented Jan 10, 2024 •
edited
Loading

You can just try

kind create cluster

without any other configuration

@BenTheElder
Copy link
Member

Please test multi nodes，I upgrade kind version, and I also get a same error。

No, we need a test with a trivial kind create cluster first so we know if it's a problem with the host for even a single, one-node cluster, or if the problem only shows up for multiple nodes + custom config options. If it doesn't show up for a single node, it's probably a resourcing issue with the host environment and we have suggestions in https://kind.sigs.k8s.io/docs/user/known-issues/, a common one is https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files which kind itself is not responsible for.

@domoran
Copy link

domoran commented Jan 12, 2024 •
edited
Loading

This problem happened to me with a "simple" cluster, but customized config:
Windows 10,
Docker Desktop 3.5.2 (66501),
Docker Engine Version: 20.10.7
Kind v0.20.0 go1.20.4 (windows/amd)

config.yaml

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  kubeadmConfigPatches:
  - |
    kind: InitConfiguration
    nodeRegistration:
      kubeletExtraArgs:
        node-labels: "ingress-ready=true"
  extraPortMappings:
  - containerPort: 80
    hostPort: 80
    protocol: TCP
  - containerPort: 443
    hostPort: 443
    protocol: TCP
  extraMounts:
   - hostPath: ./ca.crt
     containerPath: /usr/local/share/ca-certificates/ca.crt

When simply doing_

kind create cluster  --config=config.yaml               (works, control plane comes up)
kind delete cluster                                                      (works)
kind create cluster  --config=config.yaml                   (control plane would not come up)

After a reboot, it works again. Since I am using a very old version of docker engine it could be a problem of docker engine.

@SantoDE
Copy link

SantoDE commented Feb 11, 2024 •
edited
Loading

Simple kind create cluster just failed on my new installation on macOS Sonoma.

kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.29.1) 🖼
 ✓ Preparing nodes 📦
 ✗ Writing configuration 📜
Deleted nodes: ["kind-control-plane"]
ERROR: failed to create cluster: failed to copy kubeadm config to node: command "docker exec --privileged -i kind-control-plane cp /dev/stdin /kind/kubeadm.conf" failed with error: exit status 1
Command Output: Error response from daemon: Container 91347e93b6fa8b5eb7607a237a13c4935c4617a9add85cd6b08275805c40a8bd is not running

kind version
kind v0.21.0 go1.21.6 darwin/arm64

Is that linked?

@aojea
Copy link
Contributor

aojea commented Feb 12, 2024

@SantoDE see #3510

@BenTheElder
Copy link
Member

Hi folks, please file separate issues and fill out the template, even if you have the same failure message that does not mean you have the same root cause (and some of these comments don't even have the same error messages).

Closing this one due to lack of replies from the original poster and other comments not being clearly related to their case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests