kubeadm upgrade node
panics if config has KubeletConfiguration
#3161
Labels
area/upgrades
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Milestone
Not specifying a
--config
withKubeletConfiguration
for this operation works around the issue, but I thin it would be best if the config was gracefully ignored as the log message indicates.The text was updated successfully, but these errors were encountered: