-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
installing kubernetes sysext on azure doesn't autostart kubelet #50
Comments
It's a bug in the OEM sysext. The way the directory |
This is a problem for many directories:
In theory it's correct but since we want to have multiple overlays merge their contents, we should postprocess this. |
Turns out it was also masking the containerd upholds we ship through the internal containerd sysext |
Description
Kubelet is not autostarted after a reboot. In the merged /usr
ls /usr/lib/systemd/multi-user.target.d
shows that only the waagent conf is present. Manually mounting the kubernetes sysext confirms that it has a config that should uphold it.Impact
[ 1 sentence detailing the impact this bug is creating for you ]
Environment and steps to reproduce
a. [ requested the start of a new pod or container ]
b. [ container image downloaded ]
Expected behavior
[ describe what you expected to happen at 4. above but instead got an error ]
Additional information
Please add any information here that does not fit the above format.
The text was updated successfully, but these errors were encountered: