Dalton Hubble 413585681b Remove unused Kubelet lock-file and exit-on-lock-contention ... * Kubelet `--lock-file` and `--exit-on-lock-contention` date back to usage of bootkube and at one point running Kubelet in a "self-hosted" style whereby an on-host Kubelet (rkt) started pods, but then a Kubelet DaemonSet was scheduled and able to take over (hence self-hosted). `lock-file` and `exit-on-lock-contention` flags supported this pivot. The pattern has been out of favor (in bootkube too) for years because of dueling Kubelet complexity * Typhoon runs Kubelet as a container via an on-host systemd unit using podman (Fedora CoreOS) or rkt (Flatcar Linux). In fact, Typhoon no longer uses bootkube or control plane pivot (let alone Kubelet pivot) and uses static pods since v1.16.0 * https://github.com/poseidon/typhoon/pull/536		2020-06-12 00:06:41 -07:00
..
controller.yaml	Remove unused Kubelet lock-file and exit-on-lock-contention	2020-06-12 00:06:41 -07:00
install.yaml	Use strict mode for Container Linux Configs	2020-06-09 23:00:36 -07:00
worker.yaml	Remove unused Kubelet lock-file and exit-on-lock-contention	2020-06-12 00:06:41 -07:00