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
1、Using clusterctl init --infrastructure kubekey:v3.1.1 results in an error indicating that the specified version cannot be found, and when no version is specified, it defaults to installing version 3.0.13.
2、When installing the cluster using version 3.0.13, failed with error:crictl not found in system path
3、Log in to the target virtual machine and confirm that crictl exists in the $PATH(/usr/local/bin) directory, and crictl can be executed normally.
Relevant log output
E0610 15:22:46.531500 1 kkinstance_controller.go:382] "msg"="failed to reconcile phase""error"="failed to run cloud config: [init] Using Kubernetes version: v1.23.10\r\n[preflight] Running pre-flight checks\r\n[preflight] WARNING: Couldn't create the interface used for talking to the container runtime: crictl i ││ s required for container runtime: exec: \"crictl\": executable file not found in $PATH\r\n\t[WARNING FileExisting-crictl]: crictl not found in system path\r\n[preflight] Pulling images required for setting up a Kubernetes cluster\r\n[preflight] This might take a minute or two, depending on the speed of your internet co ││ nnection\r\n[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'\r\nerror execution phase preflight: crictl is required for container runtime: exec: \"crictl\": executable file not found in $PATH\r\nTo see the stack trace of this error execute with --v=5 or higher: Process exite ││ d with status 1""cluster"="kk-cluster""controller"="kkinstance""controllerGroup"="infrastructure.cluster.x-k8s.io""controllerKind"="KKInstance""kKInstance"={"name":"kk-instance-v68bd","namespace":"default"} "kkMachine"="kk-cluster-control-plane-tmtcx""machine"="kk-cluster-control-plane-tmtcx""name"="kk-instance- ││ v68bd""namespace"="default""reconcileID"="5aa533ad-169e-4d85-bf77-b8966df38e3d" │
│ E0610 15:22:46.531845 1 controller.go:326] "msg"="Reconciler error""error"="failed to run cloud config: [init] Using Kubernetes version: v1.23.10\r\n[preflight] Running pre-flight checks\r\n[preflight] WARNING: Couldn't create the interface used for talking to the container runtime: crictl is required for conta ││ iner runtime: exec: \"crictl\": executable file not found in $PATH\r\n\t[WARNING FileExisting-crictl]: crictl not found in system path\r\n[preflight] Pulling images required for setting up a Kubernetes cluster\r\n[preflight] This might take a minute or two, depending on the speed of your internet connection\r\n[preflig ││ ht] You can also perform this action in beforehand using 'kubeadm config images pull'\r\nerror execution phase preflight: crictl is required for container runtime: exec: \"crictl\": executable file not found in $PATH\r\nTo see the stack trace of this error execute with --v=5 or higher: Process exited with status 1""co ││ ntroller"="kkinstance""controllerGroup"="infrastructure.cluster.x-k8s.io""controllerKind"="KKInstance""kKInstance"={"name":"kk-instance-v68bd","namespace":"default"} "name"="kk-instance-v68bd""namespace"="default""reconcileID"="5aa533ad-169e-4d85-bf77-b8966df38e3d" │
Additional information
Clusterctl Version 1.7.2
ps: why clusterctl only support kubekey v3.0.13
The text was updated successfully, but these errors were encountered:
What is version of KubeKey has the issue?
infrastructure kubekey v3.0.13
What is your os environment?
centos 7.9
KubeKey config file
A clear and concise description of what happend.
1、Using clusterctl init --infrastructure kubekey:v3.1.1 results in an error indicating that the specified version cannot be found, and when no version is specified, it defaults to installing version 3.0.13.
2、When installing the cluster using version 3.0.13, failed with error:
crictl not found in system path
3、Log in to the target virtual machine and confirm that crictl exists in the $PATH(/usr/local/bin) directory, and crictl can be executed normally.
Relevant log output
Additional information
Clusterctl Version 1.7.2
ps: why clusterctl only support kubekey v3.0.13
The text was updated successfully, but these errors were encountered: