It appears the kubelet daemon is attempting to start before its $SNAP_DATA/args file is present. This is generated by the configure hook, so indeed it seems like a timing issue where 'start' precedes 'configure'.
A potential workaround is to manually restart kubelet-eks on the failing node (by this time, the args file should be present):
It appears the kubelet daemon is attempting to start before its $SNAP_DATA/args file is present. This is generated by the configure hook, so indeed it seems like a timing issue where 'start' precedes 'configure'.
A potential workaround is to manually restart kubelet-eks on the failing node (by this time, the args file should be present):
sudo systemctl restart snap.kubelet- eks.daemon