Skip to content
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

Flatcar fails to start due to missing /run/kubeadm/configure-kube-proxy.sh #480

Open
gabriel-samfira opened this issue Jan 16, 2025 · 0 comments · May be fixed by #481
Open

Flatcar fails to start due to missing /run/kubeadm/configure-kube-proxy.sh #480

gabriel-samfira opened this issue Jan 16, 2025 · 0 comments · May be fixed by #481

Comments

@gabriel-samfira
Copy link

The resource seems to be written to /run/kubeadm/configure-kube-proxy.sh via the ignition files directive. This happens on boot in the initrd, however, the /run folder gets recreated once the initrd pivots to the real system and executes systemd. Thus, the file will be missing in the fully booted system and kubeadm fails.

If we really need to have that file in /run, then we need to write it via a systemd unit file on Flatcar.

@gabriel-samfira gabriel-samfira linked a pull request Jan 16, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant