Create fake-node in a real cluster but nodes failed to get lease

[shadowdsp]

I want to create fake nodes in kwok in a real cluster (deployed by kubeadm), and have done the operation below.

https://kwok.sigs.k8s.io/docs/user/kwok-in-cluster/

https://kwok.sigs.k8s.io/docs/user/kwok-manage-nodes-and-pods/

But the node reports Failed to get lease: leases.coordination.k8s.io "kwok-node-1" not found , how can I do? Thanks!

kubectl describe nodes kwok-node-0
Name:               kwok-node-0
Roles:              agent
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=kwok-node-0
                    kubernetes.io/os=linux
                    kubernetes.io/role=agent
                    node-role.kubernetes.io/agent=
                    type=kwok
Annotations:        kwok.x-k8s.io/node: fake
                    node.alpha.kubernetes.io/ttl: 0
CreationTimestamp:  Mon, 18 Nov 2024 15:56:11 +0800
Taints:             node.kubernetes.io/unreachable:NoExecute
                    kwok.x-k8s.io/node=fake:NoSchedule
                    node.kubernetes.io/unreachable:NoSchedule
Unschedulable:      false
Lease:              Failed to get lease: leases.coordination.k8s.io "kwok-node-1" not found
Conditions:
  Type             Status    LastHeartbeatTime                 LastTransitionTime                Reason                   Message
  ----             ------    -----------------                 ------------------                ------                   -------
  Ready            Unknown   Mon, 18 Nov 2024 15:56:11 +0800   Mon, 18 Nov 2024 15:57:11 +0800   NodeStatusNeverUpdated   Kubelet never posted node status.
  MemoryPressure   Unknown   Mon, 18 Nov 2024 15:56:11 +0800   Mon, 18 Nov 2024 15:57:11 +0800   NodeStatusNeverUpdated   Kubelet never posted node status.
  DiskPressure     Unknown   Mon, 18 Nov 2024 15:56:11 +0800   Mon, 18 Nov 2024 15:57:11 +0800   NodeStatusNeverUpdated   Kubelet never posted node status.
  PIDPressure      Unknown   Mon, 18 Nov 2024 15:56:11 +0800   Mon, 18 Nov 2024 15:57:11 +0800   NodeStatusNeverUpdated   Kubelet never posted node status.
Addresses:
Capacity:
  cpu:     32
  memory:  256Gi
  pods:    110
Allocatable:
  cpu:     32
  memory:  256Gi
  pods:    110
System Info:
  Machine ID:
  System UUID:
  Boot ID:
  Kernel Version:
  OS Image:
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:
  Kubelet Version:            fake
  Kube-Proxy Version:         fake
PodCIDR:                      10.244.2.0/24
PodCIDRs:                     10.244.2.0/24
Non-terminated Pods:          (2 in total)
  Namespace                   Name                     CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                     ------------  ----------  ---------------  -------------  ---
  kube-flannel                kube-flannel-ds-54jdf    100m (0%)     0 (0%)      50Mi (0%)        0 (0%)         70s
  kube-system                 kube-proxy-bs2wp         0 (0%)        0 (0%)      0 (0%)           0 (0%)         70s
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests   Limits
  --------           --------   ------
  cpu                100m (0%)  0 (0%)
  memory             50Mi (0%)  0 (0%)
  ephemeral-storage  0 (0%)     0 (0%)
Events:              <none>

[wzshiming]

It seems kwok is not working, please check if it is ready, or dump kwok's log.

[shadowdsp]

It seems kwok is not working, please check if it is ready, or dump kwok's log.

You are right. The kwok controller pod is pending because the master node has taint, after adding tolerations into kwok controller, it is ok now.

Thank you very much!