Dalton Hubble 4cfafeaa07 Fix Kubelet starting before hostname set on FCOS AWS ... * Fedora CoreOS `kubelet.service` can start before the hostname is set. Kubelet reads the hostname to determine the node name to register. If the hostname was read as localhost, Kubelet will continue trying to register as localhost (problem) * This race manifests as a node that appears NotReady, the Kubelet is trying to register as localhost, while the host itself (by then) has an AWS provided hostname. Restarting kubelet.service is a manual fix so Kubelet re-reads the hostname * This race could only be shown on AWS, not on Google Cloud or Azure despite attempts. Bare-metal and DigitalOcean differ and use hostname-override (e.g. afterburn) so they're not affected * Wait for nodes to have a non-localhost hostname in the oneshot that awaits /etc/resolve.conf. Typhoon has no valid cases for a node hostname being localhost (not even single-node clusters) Related Openshift: https://github.com/openshift/machine-config-operator/pull/1813 Close https://github.com/poseidon/typhoon/issues/765		2020-06-19 00:19:54 -07:00
..
container-linux/kubernetes	Rename controller node label and NoSchedule taint	2020-06-19 00:12:13 -07:00
fedora-coreos/kubernetes	Fix Kubelet starting before hostname set on FCOS AWS	2020-06-19 00:19:54 -07:00