暂无个人介绍
2023年12月
用systemctl status kubelet命令查看,有以下问题:
kuberuntime_manager.go:1119] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to start sandbox container for pod \"kube-controller-manager-k8s-master\": Error response from daemon: failed to create task for container: failed to cre
pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"kube-controller-manager-k8s-master_kube-system(2a4133cb3bce13c258285a67e9400fd1)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\"kube-controller-ma
kubelet_node_status.go:70] "Attempting to register node" node="k8s-master"
kubelet_node_status.go:92] "Unable to register node with API server" err="Post \"https://109.105.34.101:6443/api/v1/nodes\": dial tcp 109.105.34.101:6443: connect: connection refused" node="k8s-master"
reflector.go:535] vendor/k8s.io/client-go/informers/factory.go:150: failed to list v1.Service: Get "https://109.105.34.101:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp 109.105.34.101:6443: connect: connection refused
reflector.go:147] vendor/k8s.io/client-go/informers/factory.go:150: Failed to watch v1.Service: failed to list *v1.Service: Get "https://109.105.34.101:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp 109.105.34.101:6443: connect: connection refused
pod_container_deletor.go:80] "Container not found in pod's containers" containerID="09525288e6053c7d56627693557429aa4f60cc7d7f9bf3f6ca295771fbf98f03"