You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The resource seems to be written to
/run/kubeadm/configure-kube-proxy.sh
via the ignitionfiles
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.The text was updated successfully, but these errors were encountered: