Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
Kubernetes Service (AKS): Node Shows in NotReady State and Pod Operations Stuck — Assistance Needed
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 3%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EO3%3C/text%3E%3C/svg%3E)
OussamaELKHAYALI-3837
0
Reputation points
Problem description
I am experiencing an issue with my Azure Kubernetes Service (AKS). The worker node is partially unresponsive, with the VM agent unavailable and pod operations stuck. Although production traffic was restored after relocating the gateway, the affected node remains in a NotReady state, and certain pod operations are not progressing.
Environment
Azure Kubernetes Service, Node in NotReady State, in an unspecified region.
What I've already tried
I relocated the console and management API replicas; requested eviction of remaining non-DaemonSet pods; monitored node and cluster status; and checked cluster data for common issues. However, the node remains cordoned and unresponsive.
Current status
I am seeking further assistance to diagnose the root cause of the node hang and to determine the appropriate next steps to restore full node health and stability.
Azure Kubernetes Service
1 answer
Sort by: Newest
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more