-
Notifications
You must be signed in to change notification settings - Fork 29
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
Kubernetes support: To work by default, ship a symlink in /usr/libexec #1193
Comments
The symlink for the directory in /usr/libexec has to be created like a file or otherwise it will land inside the existing directory (which shouldn't have existed). Fix the symlink creation. A better solution would be flatcar/Flatcar#1193 but that's for future releases.
with this we might be able to get rid of https://github.com/flatcar/mantle/blob/fbb5dee5e8e610cec56e7040c74bf2c6c1e3096a/kola/tests/kubeadm/templates.go#L365 |
@pothos How would I use your workaround for my setup (now)? I need to move |
You can ship the symlink with a systemd-sysext folder (or .raw image) like done here https://github.com/flatcar/sysext-bakery/blob/main/create_kubernetes_sysext.sh#L85 |
@pothos is there a way without using systemd-sysext? I didn't want to go down that rabbithole 🐇 🕳️ right now |
This is how you can configure an own path in Kubernetes |
Ok, doing something like that. Just figured I could maybe do this easier. Thank you! |
Current situation
Kubernetes tries to write files to
/usr/libexec/kubernetes/kubelet-plugins/volume/exec/
which fails on Flatcar.Workarounds were bind mounts or a sysext with a symlink.
Impact
Does not work by default.
Ideal future situation
/usr/libexec/kubernetes/kubelet-plugins/volume/exec
is a symlink to/var/kubernetes/kubelet-plugins/volume/exec
in the generic image. A tmpfile rule creates the symlink during image build time and also the target at runtime.The text was updated successfully, but these errors were encountered: