Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
manifests: updater mount the directory, not the socket
Quoting kube docs: ``` when accessing the `/var/lib/kubelet/pod-resources/kubelet.sock` from DaemonSet or any other app deployed as a container on the host, which is mounting socket as a volume, it is a good practice to mount directory `/var/lib/kubelet/pod-resources/` instead of the `/var/lib/kubelet/pod-resources/kubelet.sock`. This will ensure that after kubelet restart, container will be able to re-connect to this socket. Container mounts are managed by inode referencing the socket or directory, depending on what was mounted. When kubelet restarts, socket is deleted and a new socket is created, while directory stays untouched. So the original inode for the socket become unusable. Inode to directory will continue working. ``` Signed-off-by: Francesco Romani <[email protected]>
- Loading branch information