AKS Windows Node problem after 1.22 upgrade
Read OriginalA detailed technical account of troubleshooting an Azure Kubernetes Service (AKS) cluster after upgrading from version 1.21.4 to 1.22.4. The article documents two specific problems: a Linux node pool scaling inconsistency and a critical Windows node pool issue where nodes were not visible to kubectl. It details the diagnostic process, including accessing Windows nodes via RDP, examining kubelet logs, and identifying a configuration error related to the deprecated DynamicKubeletConfig feature gate.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser