Troubleshooting
Problem
Since the cluster was installed you have always seen the same age for all the nodes of the cluster when you ran "kubectl get nodes". But recently you are seeing different values for the age. You are not sure why these values have changed and if could potentially impact the performance of the cluster? The node in question has been rebooted recently but an OS reboot normally doesn't change the age of a kubernetes node.
Resolving The Problem
The age of a cluster node is really based on creation, not modification. Maybe a new compute node has been added to the cluster which could explain the age difference?
In the end it doesn’t really matter what age it shows, it's just what the apiserver picks up… maybe a name was changed, changed back… hard to say… as long as the nodes you are seeing are the ones you expect to see.
In the end it doesn’t really matter what age it shows, it's just what the apiserver picks up… maybe a name was changed, changed back… hard to say… as long as the nodes you are seeing are the ones you expect to see.
So the difference is really insignificant and the online kubernetes documentation could provide more information.
Document Location
Worldwide
[{"Type":"SW","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHGWL","label":"IBM Watson Studio Local"},"ARM Category":[{"code":"a8m0z000000bmvTAAQ","label":"Admin->Node admin"}],"ARM Case Number":"TS005413734","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
20 April 2021
UID
ibm16445387