Почему не запускается kubelet.service?

О чем говорит ошибка отсутствия /var/run/containerd/containerd.sock ?

Первая тестовая установка kubernetes.
Firewall, swap отключены.

Сразу после установки сервис запустился

amk:~ # kubectl get nodes
NAME                   STATUS     ROLES           AGE     VERSION
amk                    NotReady   control-plane   4m17s   v1.25.4


но после перезагрузки (в преднастройках потребовал 2 виртуальных ядра) перестал запускаться

# kubectl get nodes
The connection to the server 192.168.29.65:6443 was refused - did you specify the right host or port?


в логе ошибка failed to connect
и отсутствие файла /var/run/containerd/containerd.sock

сервис docker.service
● docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: disabled)
     Active: active (running)


journalctl

Nov 11 18:16:14 amk systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 105.
Nov 11 18:16:14 amk systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Nov 11 18:16:14 amk systemd[1]: Started kubelet: The Kubernetes Node Agent.
Nov 11 18:16:14 amk kubelet[25907]: Flag --container-runtime has been deprecated, will be removed in 1.27 as the only valid value is 'remote'
Nov 11 18:16:14 amk kubelet[25907]: Flag --pod-infra-container-image has been deprecated, will be removed in 1.27. Image garbage collector will get sandbox image information from CRI.
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.365507   25907 server.go:200] "--pod-infra-container-image will not be pruned by the image garbage collector in kubelet and should also be set in the remote runtime"
Nov 11 18:16:14 amk kubelet[25907]: Flag --container-runtime has been deprecated, will be removed in 1.27 as the only valid value is 'remote'
Nov 11 18:16:14 amk kubelet[25907]: Flag --pod-infra-container-image has been deprecated, will be removed in 1.27. Image garbage collector will get sandbox image information from CRI.
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.368075   25907 server.go:413] "Kubelet version" kubeletVersion="v1.25.4"
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.368158   25907 server.go:415] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.368325   25907 server.go:825] "Client rotation is on, will bootstrap in background"
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.369342   25907 certificate_store.go:130] Loading cert/key pair from "/var/lib/kubelet/pki/kubelet-client-current.pem".
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.369988   25907 dynamic_cafile_content.go:157] "Starting controller" name="client-ca-bundle::/etc/kubernetes/pki/ca.crt"
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.373035   25907 server.go:660] "--cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /"
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.373299   25907 container_manager_linux.go:262] "Container manager verified user specified cgroup-root exists" cgroupRoot=[]
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.373371   25907 container_manager_linux.go:267] "Creating Container Manager object based on Node Config" nodeConfig={RuntimeCgroupsName: SystemCgroupsName: KubeletCgroupsName: KubeletOOMScoreAdj:-999 ContainerRuntime: CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:systemd KubeletRootDir:/var/lib/kubelet ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: ReservedSystemCPUs: EnforceNodeAllocatable:map[pods:{}] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[{Signal:memory.available Operator:LessThan Value:{Quantity:100Mi Percentage:0} GracePeriod:0s MinReclaim:<nil>} {Signal:nodefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.1} GracePeriod:0s MinReclaim:<nil>} {Signal:nodefs.inodesFree Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>} {Signal:imagefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.15} GracePeriod:0s MinReclaim:<nil>}]} QOSReserved:map[] ExperimentalCPUManagerPolicy:none ExperimentalCPUManagerPolicyOptions:map[] ExperimentalTopologyManagerScope:container ExperimentalCPUManagerReconcilePeriod:10s ExperimentalMemoryManagerPolicy:None ExperimentalMemoryManagerReservedMemory:[] ExperimentalPodPidsLimit:-1 EnforceCPULimits:true CPUCFSQuotaPeriod:100ms ExperimentalTopologyManagerPolicy:none}
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.373399   25907 topology_manager.go:134] "Creating topology manager with policy per scope" topologyPolicyName="none" topologyScopeName="container"
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.373416   25907 container_manager_linux.go:302] "Creating device plugin manager" devicePluginEnabled=true
Nov 11 18:16:14 amk kubelet[25907]: I1111 18:16:14.373453   25907 state_mem.go:36] "Initialized new in-memory state store"
Nov 11 18:16:14 amk kubelet[25907]: W1111 18:16:14.373738   25907 logging.go:59] [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
Nov 11 18:16:14 amk kubelet[25907]:   "Addr": "/var/run/containerd/containerd.sock",
Nov 11 18:16:14 amk kubelet[25907]:   "ServerName": "/var/run/containerd/containerd.sock",
Nov 11 18:16:14 amk kubelet[25907]:   "Attributes": null,
Nov 11 18:16:14 amk kubelet[25907]:   "BalancerAttributes": null,
Nov 11 18:16:14 amk kubelet[25907]:   "Type": 0,
Nov 11 18:16:14 amk kubelet[25907]:   "Metadata": null
Nov 11 18:16:14 amk kubelet[25907]: }. Err: connection error: desc = "transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory"
Nov 11 18:16:14 amk kubelet[25907]: E1111 18:16:14.373801   25907 run.go:74] "command failed" err="failed to run Kubelet: unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
Nov 11 18:16:14 amk systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
Nov 11 18:16:14 amk systemd[1]: kubelet.service: Failed with result 'exit-code'.
  • Вопрос задан
  • 85 просмотров
Пригласить эксперта
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы