Go to file
Boovan Rajendran 59fd01b093 Reduce kubelet.service startup failure errors during node installation
During node install/reinstall there is lot of kubelet.service startup
failure errors occurs. This adds systemd ConditionPathExists to
kubelet.service to prevent kubelet from starting before necessary
configuration files are created during bootstrap of a Kubernetes node

Note:
The kubelet.service requires the following configuration files to
start successfully:
/etc/default/kubelet
/etc/kubernetes/kubelet.conf
/var/lib/kubelet/config.yaml

we are intentionally excluding /etc/kubernetes/kubelet.conf from
this change. This is because during the kubeadm join process, the
kubelet is started before this file is generated. Adding a systemd
condition that checks for the existence of /etc/kubernetes/kubelet.conf
will cause the kubelet to fail to start, resulting in the kubeadm join
command failing due to an unhealthy kubelet.

Test Plan:
PASS: Install ISO as AIO-SX,AIO-DX and Standard, verify
kubelet.service starts properly and start errors are reduced.
PASS: Perform factory install using dc-libvirt and verify
kubelet.service starts properly and start errors are reduced.

Closes-Bug: 2125480

Change-Id: Iaf89ac8f87bf3981d72bf091c53709ebc5f1d72e
Signed-off-by: Boovan Rajendran <boovan.rajendran@windriver.com>
2025-09-29 06:31:46 -04:00
2023-08-29 16:52:04 -03:00
2024-05-01 16:39:19 -04:00
2024-05-01 16:39:19 -04:00
2019-01-08 11:42:04 -05:00
2019-04-19 19:52:31 +00:00
2023-09-06 17:54:55 -03:00
2021-09-09 19:05:36 +03:00
2018-05-31 07:36:35 -07:00
2025-03-10 09:13:52 -03:00

integ

StarlingX Integration

Description
StarlingX Integration and packaging
Readme 55 MiB
Languages
Shell 28%
Python 22.6%
JavaScript 21.4%
Perl 12.7%
C++ 5.7%
Other 9.5%