Master node status was “Ready” but once the worker nodes have been added to the clusters, the status changed to “NotReady”. Has anyone encountered the same problem?
I would greatly appreciate it if someone could dig in deeper into analyzing the issue.
Installation method: Virtual Machine (VMware ESXi)
OS: Ubuntu 22.04
$kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-master NotReady control-plane 3d8h v1.27.2
k8s-worker1 Ready 162m v1.27.2
k8s-worker2 Ready 139m v1.27.1
k8s-worker3 Ready 132m v1.27.1
$kubectl describe nodes k8s-master
Name: k8s-master.dcs2.local
Roles: control-plane
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=k8s-master.dcs2.local
kubernetes.io/os=linux
node-role.kubernetes.io/control-plane=
node.kubernetes.io/exclude-from-external-load-balancers=
Annotations: csi.volume.kubernetes.io/nodeid: {“csi.tigera.io”:“k8s-master.dcs2.local”}
kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock
node.alpha.kubernetes.io/ttl: 0
projectcalico.org/IPv4Address: 192.168.1.165/24
projectcalico.org/IPv4VXLANTunnelAddr: 192.168.27.0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp: Sun, 04 Jun 2023 18:11:51 +0000
Taints: node.kubernetes.io/unreachable:NoExecute
node.kubernetes.io/unreachable:NoSchedule
Unschedulable: false
Lease:
HolderIdentity: k8s-master.dcs2.local
AcquireTime:
RenewTime: Wed, 07 Jun 2023 23:30:38 +0000
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
NetworkUnavailable False Wed, 07 Jun 2023 23:24:12 +0000 Wed, 07 Jun 2023 23:24:12 +0000 CalicoIsUp Calico is running on this node
MemoryPressure Unknown Wed, 07 Jun 2023 23:28:46 +0000 Wed, 07 Jun 2023 23:34:07 +0000 NodeStatusUnknown Kubelet stopped posting node status.
DiskPressure Unknown Wed, 07 Jun 2023 23:28:46 +0000 Wed, 07 Jun 2023 23:34:07 +0000 NodeStatusUnknown Kubelet stopped posting node status.
PIDPressure Unknown Wed, 07 Jun 2023 23:28:46 +0000 Wed, 07 Jun 2023 23:34:07 +0000 NodeStatusUnknown Kubelet stopped posting node status.
Ready Unknown Wed, 07 Jun 2023 23:28:46 +0000 Wed, 07 Jun 2023 23:34:07 +0000 NodeStatusUnknown Kubelet stopped posting node status.
Addresses:
InternalIP: 192.168.1.165
Hostname: k8s-master.dcs2.local
Capacity:
cpu: 2
ephemeral-storage: 39937312Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 3052260Ki
pods: 110
Allocatable:
cpu: 2
ephemeral-storage: 36806226679
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 2949860Ki
pods: 110
System Info:
Machine ID: 6566e1f7fa984422bd1cb6a447d68f9f
System UUID: a20e4d56-9c0f-0de9-b4c8-bb241947eaaf
Boot ID: e807cfae-dfa0-4ef0-8242-23591e569c46
Kernel Version: 5.15.0-73-generic
OS Image: Ubuntu 22.04.2 LTS
Operating System: linux
Architecture: amd64
Container Runtime Version: containerd://1.6.12
Kubelet Version: v1.27.2
Kube-Proxy Version: v1.27.2
PodCIDR: 192.168.0.0/24
PodCIDRs: 192.168.0.0/24
Non-terminated Pods: (14 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age
calico-apiserver calico-apiserver-6b5dddb9cb-j8x22 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d5h
calico-apiserver calico-apiserver-6b5dddb9cb-sssj7 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d5h
calico-system calico-kube-controllers-6c7c8cdd96-n6r42 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d5h
calico-system calico-node-wpdmg 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d5h
calico-system calico-typha-6f9dc66495-zhltk 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d5h
calico-system csi-node-driver-m5pxr 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d5h
kube-system coredns-5d78c9869d-qk2zd 100m (5%) 0 (0%) 70Mi (2%) 170Mi (5%) 3d8h
kube-system coredns-5d78c9869d-w4lvz 100m (5%) 0 (0%) 70Mi (2%) 170Mi (5%) 3d8h
kube-system etcd-k8s-master.dcs2.local 100m (5%) 0 (0%) 100Mi (3%) 0 (0%) 3d8h
kube-system kube-apiserver-k8s-master.dcs2.local 250m (12%) 0 (0%) 0 (0%) 0 (0%) 3d8h
kube-system kube-controller-manager-k8s-master.dcs2.local 200m (10%) 0 (0%) 0 (0%) 0 (0%) 3d8h
kube-system kube-proxy-f4lwf 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d8h
kube-system kube-scheduler-k8s-master.dcs2.local 100m (5%) 0 (0%) 0 (0%) 0 (0%) 3d8h
tigera-operator tigera-operator-58f95869d6-x24hx 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3d7h
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
cpu 850m (42%) 0 (0%)
memory 240Mi (8%) 340Mi (11%)
ephemeral-storage 0 (0%) 0 (0%)
hugepages-1Gi 0 (0%) 0 (0%)
hugepages-2Mi 0 (0%) 0 (0%)
Events: