-
Notifications
You must be signed in to change notification settings - Fork 14k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node Status Discrepancy #810
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement:
There is a discrepancy in the node status visibility between two different environments in the Kubernetes cluster.
Details:
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.
On the Control Node:
When running the same
kubectl get nodes
command from the control node with theadmin.kubeconfig
file, the following output is observed: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.
The text was updated successfully, but these errors were encountered: