☰

未找到 kubelet 節點

tag-icon • tag-icon docker kubernetes kubeadm
未找到 kubelet 節點

我正在嘗試建立一個 kubernetes 叢集。我kubeadm init與 The 的時光kubelet is unhealthy due to a misconfiguration of the node in some way。看看 Kubelet，我發現它正在不斷報告Container runtime network not ready, Error getting node, 和Nameserver limits exceeded。

環顧類似的問題，我發現現有針對類似問題的解決方案不起作用或沒有意義：

  1. 一位候選人是我缺少 pod 網路插件但這是透過使用kubectl apply -f安裝 pod 網路來解決的，我無法這樣做，因為 kubectl 無法在沒有現有集群的情況下運行（我無法建立集群，因此出現了問題）。
  2. 另一位候選人是我還沒有正確安裝了docker讓 kublet 找到它，但這沒有意義，因為 cri-docker 正在運行並且似乎很好（見下文）
  3. 條目太多在我的/etc/resolve.conf- 我檢查過，我只有一個條目。
● cri-docker.service - CRI Interface for Docker Application Container Engine
     Loaded: loaded (/etc/systemd/system/cri-docker.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2022-11-19 17:04:57 UTC; 3h 31min ago
TriggeredBy: ● cri-docker.socket
       Docs: https://docs.mirantis.com
   Main PID: 1522 (cri-dockerd)
      Tasks: 30
     Memory: 51.6M
        CPU: 41.468s
     CGroup: /system.slice/cri-docker.service
             └─1522 /usr/local/bin/cri-dockerd --container-runtime-endpoint fd://

sudo journalctl -xeu kubelet給我：

● kubelet.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/kubelet.service.d
             └─10-kubeadm.conf
     Active: active (running) since Sat 2022-11-19 19:59:33 UTC; 39min ago
       Docs: https://kubernetes.io/docs/home/
   Main PID: 33473 (kubelet)
      Tasks: 36 (limit: 76768)
     Memory: 37.5M
        CPU: 39.709s
     CGroup: /system.slice/kubelet.service
             └─33473 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --container-runtime=remote --container-ru>

Nov 19 20:38:33 master-node kubelet[33473]: E1119 20:38:33.296924   33473 kubelet.go:2448] "Error getting node" err="node \"node\" not found"
...
kubelet.go:2448] "Error getting node" err="node \"node\" not found"
Nov 19 20:38:47 master-node kubelet[33473]: E1119 20:38:47.474190   33473 event.go:276] Unable to write event: '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"node.172914c534e4e80a">
Nov 19 20:38:47 master-node kubelet[33473]: E1119 20:38:47.501529   33473 kubelet.go:2448] "Error getting node" err="node \"node\" not found"
...
kubelet.go:2448] "Error getting node" err="node \"node\" not found"
Nov 19 20:38:50 master-node kubelet[33473]: E1119 20:38:50.044530   33473 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin>
Nov 19 20:38:50 master-node kubelet[33473]: W1119 20:38:50.075372   33473 reflector.go:424] vendor/k8s.io/client-go/informers/factory.go:134: failed to list *v1.RuntimeClass: Get "https://1.2.3.4:6443/apis/node.k8s.io/v1/>
Nov 19 20:38:50 master-node kubelet[33473]: I1119 20:38:50.075518   33473 trace.go:205] Trace[23698761]: "Reflector ListAndWatch" name:vendor/k8s.io/client-go/informers/factory.go:134 (19-Nov-2022 20:38:20.073) (total tim>
Nov 19 20:38:50 master-node kubelet[33473]: Trace[23698761]: ---"Objects listed" error:Get "https://1.2.3.4:6443/apis/node.k8s.io/v1/runtimeclasses?limit=500&resourceVersion=0": dial tcp 1.2.3.4:6443: i/o timeout 30001ms >
Nov 19 20:38:50 master-node kubelet[33473]: Trace[23698761]: [30.00168996s] [30.00168996s] END
Nov 19 20:38:50 master-node kubelet[33473]: E1119 20:38:50.075544   33473 reflector.go:140] vendor/k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.RuntimeClass: failed to list *v1.RuntimeClass: Get "https:/>
Nov 19 20:38:50 master-node kubelet[33473]: E1119 20:38:50.120558   33473 kubelet.go:2448] "Error getting node" err="node \"node\" not found"
...

我傳給的 kube-config.yaml kubeadm init --config kube-config.yaml：

apiVersion: kubeadm.k8s.io/v1beta3
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  advertiseAddress: 1.2.3.4
  bindPort: 6443
nodeRegistration:
  criSocket: unix:///var/run/cri-dockerd.sock
  imagePullPolicy: IfNotPresent
  name: node
  taints: null
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta3
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns: {}
etcd:
  local:
    dataDir: /var/lib/etcd
imageRepository: registry.k8s.io
kind: ClusterConfiguration
kubernetesVersion: 1.25.0
networking:
  dnsDomain: cluster.local
  serviceSubnet: 10.96.0.0/12
scheduler: {}
---
kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
cgroupDriver: systemd

這裡出了什麼問題？

相關內容