This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
Bad hosted kubelet configuration leaves node logs unreachable #1579
Labels
kind/enhancement
New feature or request
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems when you specify a bad flag for kubelet, then it enters the restart loop and host kubelet does not have time to kick in and take over. Maybe this could be improved.
The text was updated successfully, but these errors were encountered: