A new worker node entry appears in the kubectl output with the name 127.0.0.1
# kubectl get nodes
NAME STATUS ROLES AGE VERSION
127.0.0.1 NotReady,SchedulingDisabled worker 17h v1.17.6
- Platform9 Managed Kubernetes - v4.3 and below
- The new worker node entry is created if there was a maintenance activity performed during which a default route was missing on any of the worker nodes.
- When a default route is missing, the pf9-kube script picks up the first available IP from the node and which happens to be of the loopback interface.
- This is a known issue and has been fixed starting v4.4.
- Confirm that all the actual worker nodes in the cluster are in a ready state.
- Check for the pods running on the newly created worker node 127.0.0.1.
- If there are no workloads running on the node other than any Daemonsets, please go ahead and delete the node using the following command.
$ kubectl delete node 127.0.0.1