169a0c0ee3
This introduces k8s-container-cleanup script that will be called
when containerd.service is stopped. The script detects whether systemd
state is 'stopping' due to shutdown/reboot, then stops all running
containers before the service shuts down.
During shutdown/reboot, some containers are not receiving the
SIGTERM signal. This leads to unexpected behaviour such as
generating huge coredumps.
There is an upstream issue regarding this:
https://github.com/kubernetes/kubernetes/issues/107158
The problem seems to be systemd related but this commit
addresses the problem with a workaround.
This reverts commit
|
||
---|---|---|
.. | ||
enable-support-for-kubernetes-to-ignore-isolcpus.patch | ||
kubeadm-create-platform-pods-with-zero-CPU-resources.patch | ||
kubeadm.conf | ||
kubelet-cgroup-setup.sh | ||
kubelet-cpumanager-disable-CFS-quota-throttling-for-.patch | ||
kubelet-cpumanager-infrastructure-pods-use-system-re.patch | ||
kubelet-cpumanager-introduce-concept-of-isolated-CPU.patch | ||
kubelet-cpumanager-keep-normal-containers-off-reserv.patch | ||
kubelet-sort-isolcpus-allocation-when-SMT-enabled.patch | ||
kubernetes-make-isolcpus-allocation-SMT-aware.patch | ||
Revert-use-subpath-for-coredns-only-for-default-repo.patch |