0180.K kubelet.go 2466 Error getting node not found

[root@k8s3-master ~]# kubeadm init --apiserver-advertise-address=192.168.90.125 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.23.8 --service-cidr=10.96.0.0/12 --pod-network-cidr=10.244.0.0/16[init] Using Kubernetes version: v1.23.8[preflight] Running pre-flight checks...[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"[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[kubelet-check] Initial timeout of 40s passed.      #执行超过40s
  Unfortunately, an error has occurred:    timed out waiting for the condition
  This error is likely caused by:    - The kubelet is not running    - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
  If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:    - 'systemctl status kubelet'    - 'journalctl -xeu kubelet'
  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.
  Here is one example how you may list all Kubernetes containers running in docker:    - 'docker ps -a | grep kube | grep -v pause'    Once you have found the failing container, you can inspect its logs with:    - 'docker logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster      #初始化失败To see the stack trace of this error execute with --v=5 or higher

[root@k8s3-master ~]# systemctl status kubelet● kubelet.service - kubelet: The Kubernetes Node Agent   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)  Drop-In: /usr/lib/systemd/system/kubelet.service.d           └─10-kubeadm.conf   Active: active (running) since Wed 2022-07-06 17:27:00 CST; 49s ago     Docs: https://kubernetes.io/docs/ Main PID: 80133 (kubelet)    Tasks: 26   Memory: 32.1M   CGroup: /system.slice/kubelet.service           └─80133 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --network-plugin=cni --pod-infra-container-image=regist...
Jul 06 17:27:49 k8s3-master kubelet[80133]: E0706 17:27:49.660120   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:49 k8s3-master kubelet[80133]: E0706 17:27:49.760811   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:49 k8s3-master kubelet[80133]: E0706 17:27:49.861505   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:49 k8s3-master kubelet[80133]: I0706 17:27:49.957202   80133 kubelet_node_status.go:70] "Attempting to register node" node="k8s3-master"Jul 06 17:27:49 k8s3-master kubelet[80133]: E0706 17:27:49.962534   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:49 k8s3-master kubelet[80133]: E0706 17:27:49.998194   80133 kubelet_node_status.go:92] "Unable to register node with API server" err="Post \"https://192.168.90.125:6443/api/v1/nodes\": dial tcp 192.168....ode="k8s3-master"Jul 06 17:27:50 k8s3-master kubelet[80133]: E0706 17:27:50.063267   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:50 k8s3-master kubelet[80133]: E0706 17:27:50.163691   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:50 k8s3-master kubelet[80133]: E0706 17:27:50.264587   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"Jul 06 17:27:50 k8s3-master kubelet[80133]: E0706 17:27:50.365572   80133 kubelet.go:2466] "Error getting node" err="node \"k8s3-master\" not found"

[root@k8s3-master ~]# hostnamek8s3-master

[root@k8s3-master ~]# cat /etc/hostname k8s3-master

[root@k8s3-master ~]# cat /etc/hosts127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.80.125 k8s3-master192.168.80.126 k8s3-node1192.168.80.127 k8s3-node2

[root@k8s3-master ~]# kubeadm reset -f

systemctl daemon-reload && systemctl restart kubelet && systemctl status kubelet

[root@k8s3-master ~]# kubeadm init --apiserver-advertise-address=192.168.80.125 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.23.8 --service-cidr=10.96.0.0/12 --pod-network-cidr=10.244.0.0/16 --v=5...Your Kubernetes control-plane has initialized successfully!...

  advertiseAddress: 192.168.80.125  #1. 更改为master ip  bindPort: 6443nodeRegistration:  criSocket: unix:///var/run/containerd/containerd.sock  imagePullPolicy: IfNotPresent  name: master1                    #2. 更改为master主机名