Meizuamy
commented
2 years ago some issue like picture shown us
Closed Meizuamy closed 2 years ago
Meizuamy
commented
2 years ago some issue like picture shown us
Meizuamy
commented
2 years ago Creating cluster "kubeflow" ... ✓ Ensuring node image (kindest/node:v1.16.9) 🖼 ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✗ Starting control-plane 🕹️ ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kubeflow-control-plane kubeadm init --skip-phases=preflight --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1 Command Output: I0702 04:36:24.085419 196 initconfiguration.go:190] loading configuration from "/kind/kubeadm.conf" [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration I0702 04:36:24.089725 196 feature_gate.go:216] feature gates: &{map[]} I0702 04:36:24.089894 196 kubelet.go:61] Stopping the kubelet [init] Using Kubernetes version: v1.16.9 [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" I0702 04:36:24.108059 196 kubelet.go:79] Starting the kubelet [kubelet-start] Activating the kubelet service I0702 04:36:24.176010 196 certs.go:104] creating a new certificate authority for ca [certs] Using certificateDir folder "/etc/kubernetes/pki" [certs] Generating "ca" certificate and key [certs] Generating "apiserver" certificate and key [certs] apiserver serving cert is signed for DNS names [kubeflow-control-plane kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local kubeflow-control-plane localhost] and IPs [10.96.0.1 172.18.0.2 127.0.0.1] [certs] Generating "apiserver-kubelet-client" certificate and key I0702 04:36:24.746337 196 certs.go:104] creating a new certificate authority for front-proxy-ca [certs] Generating "front-proxy-ca" certificate and key [certs] Generating "front-proxy-client" certificate and key I0702 04:36:24.983126 196 certs.go:104] creating a new certificate authority for etcd-ca [certs] Generating "etcd/ca" certificate and key [certs] Generating "etcd/server" certificate and key [certs] etcd/server serving cert is signed for DNS names [kubeflow-control-plane localhost] and IPs [172.18.0.2 127.0.0.1 ::1] [certs] Generating "etcd/peer" certificate and key [certs] etcd/peer serving cert is signed for DNS names [kubeflow-control-plane localhost] and IPs [172.18.0.2 127.0.0.1 ::1] [certs] Generating "etcd/healthcheck-client" certificate and key [certs] Generating "apiserver-etcd-client" certificate and key I0702 04:36:26.217854 196 certs.go:70] creating a new public/private key files for signing service account users [certs] Generating "sa" key and public key I0702 04:36:26.374751 196 kubeconfig.go:79] creating kubeconfig file for admin.conf [kubeconfig] Using kubeconfig folder "/etc/kubernetes" [kubeconfig] Writing "admin.conf" kubeconfig file I0702 04:36:26.465743 196 kubeconfig.go:79] creating kubeconfig file for kubelet.conf [kubeconfig] Writing "kubelet.conf" kubeconfig file I0702 04:36:26.619571 196 kubeconfig.go:79] creating kubeconfig file for controller-manager.conf [kubeconfig] Writing "controller-manager.conf" kubeconfig file I0702 04:36:26.777319 196 kubeconfig.go:79] creating kubeconfig file for scheduler.conf [kubeconfig] Writing "scheduler.conf" kubeconfig file [control-plane] Using manifest folder "/etc/kubernetes/manifests" [control-plane] Creating static Pod manifest for "kube-apiserver" I0702 04:36:27.112360 196 manifests.go:91] [control-plane] getting StaticPodSpecs I0702 04:36:27.120182 196 manifests.go:116] [control-plane] wrote static Pod manifest for component "kube-apiserver" to "/etc/kubernetes/manifests/kube-apiserver.yaml" I0702 04:36:27.120231 196 manifests.go:91] [control-plane] getting StaticPodSpecs [control-plane] Creating static Pod manifest for "kube-controller-manager" [control-plane] Creating static Pod manifest for "kube-scheduler" I0702 04:36:27.121125 196 manifests.go:116] [control-plane] wrote static Pod manifest for component "kube-controller-manager" to "/etc/kubernetes/manifests/kube-controller-manager.yaml" I0702 04:36:27.121169 196 manifests.go:91] [control-plane] getting StaticPodSpecs [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests" I0702 04:36:27.121897 196 manifests.go:116] [control-plane] wrote static Pod manifest for component "kube-scheduler" to "/etc/kubernetes/manifests/kube-scheduler.yaml" I0702 04:36:27.122632 196 local.go:69] [etcd] wrote Static Pod manifest for a local etcd member to "/etc/kubernetes/manifests/etcd.yaml" I0702 04:36:27.122667 196 waitcontrolplane.go:80] [wait-control-plane] Waiting for the API server to be healthy I0702 04:36:27.123408 196 loader.go:375] 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 I0702 04:36:27.125866 196 round_trippers.go:443] GET https://kubeflow-control-plane:6443/healthz?timeout=32s in 1 milliseconds ...... I0702 04:38:22.127981 196 round_trippers.go:443] GET https://kubeflow-control-plane:6443/healthz?timeout=32s in 1 milliseconds [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:
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
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, e.g. docker. Here is one example how you may list all Kubernetes containers running in docker:
wangjiangyong
commented
2 years ago nice
update kindest/node version 1.16.9 -> 1.16.15. we use kindest/node:1.16.9 can't start k8s cluster.