Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Restart kubelet if it does not report an internal/external ip address
On kubelet start-up some functions to set the node status are generated. One of those functions propagates the node addresses into the `Node` object the kubelet is responsible for (`.status.addresses`). The kube-apiserver uses these addresses to talk to the actual node. To identify the IP address of the node the kubelet communicates with the cloud provider. kubernetes/kubernetes#62543 introduced a timeout of 10s when trying to connect to the cloud. In case the IP cannot be determined within 10s, the `Node` object does not report an `InternalIP` address. Consequently, the kube-apiserver will never be able to talk to that node; particularly VPN won't work in case the vpn-shoot pod is scheduled on it. Once the connection failed, it is never retried, and only a kubelet process restart can trigger it again. Hence, our kubelet monitoring script will now do the same when it cannot find an `InternalIP` or an `ExternalIP` address on the `Node` object. closes gardener#283
- Loading branch information