Node Status Discrepancy

[Konami33]

Problem Statement:

There is a discrepancy in the node status visibility between two different environments in the Kubernetes cluster.

Details:

1. On the Local Machine:

   When running the kubectl get nodes command directly from the local machine used to generate all the admin client certificates, the following output is observed:

   root@8a08ed99cb7f4ee3:~/code# kubectl get nodes
   NAME           AGE
   ip-10-0-1-20   1h
   ip-10-0-1-21   1h

   Note: The node status is not displayed, only the names and ages of the nodes are shown.

2. On the Control Node:

   When running the same kubectl get nodes command from the control node with the admin.kubeconfig file, the following output is observed:

   ubuntu@controller-0:~$ kubectl get nodes --kubeconfig admin.kubeconfig
   NAME           STATUS   ROLES    AGE    VERSION
   ip-10-0-1-20   Ready    <none>   117m   v1.21.0
   ip-10-0-1-21   Ready    <none>   117m   v1.21.0

   Note: The node status, roles, age, and version are correctly displayed.

Observation:

The local machine used for certificate generation does not show the node statuses, while the control node correctly shows the status of each node as Ready, along with additional information such as roles, age, and version.

Request for Assistance:

Please investigate the potential reasons for this discrepancy and provide guidance on how to align the node status visibility between the local machine and the control node. Any insights into configuration differences or potential issues would be appreciated.