Update node-not-ready-then-recovers.md

Changes in the right branch following the PR: https://github.com/VictoriaNoje/SupportArticles-docs-pr/pull/1/files

Author: reknai

support/azure/azure-kubernetes/availability-performance/node-not-ready-then-recovers.md

@@ -1,7 +1,7 @@
 ---
 title: Node not ready but then recovers
 description: Troubleshoot scenarios in the status of an Azure Kubernetes Service (AKS) cluster node is Node Not Ready, but then the node recovers.
-ms.date: 04/15/2022
+ms.date: 10/15/2024
 ms.reviewer: rissing, chiragpa, momajed, v-leedennis
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to prevent the Node Not Ready status for nodes that later recover so that I can avoid future errors within an Azure Kubernetes Service (AKS) cluster.
@@ -13,29 +13,30 @@ This article helps troubleshoot scenarios in which a node within a Microsoft Azu
 
 ## Symptoms
 
-You notice that your application stops responding while the node is reporting that it has a Not Ready status. However, the node recovers automatically, and now, it's looking for a root cause analysis (RCA).
+Maintaining node readiness in Azure Kubernetes Service (AKS) clusters is crucial for ensuring application availability and performance. When a node enters a "Not Ready" state, it can disrupt the application's functionality, causing it to stop responding. Although the node typically recovers automatically after a short period, understanding the underlying causes and implementing effective resolutions is essential to prevent recurring issues and maintain a stable environment. This document provides a comprehensive guide to troubleshooting and resolving node readiness issues in AKS clusters.
 
 ## Cause
 
-Possible causes of this issue include the following scenarios:
+There are several scenarios that could lead to this issue:
 
-- The API server isn't available, and you're using a readiness probe for the deployment.
-
-  If a pod is running but isn't ready, that situation means that the readiness probe is failing. If the readiness probe fails, the pod isn't attached to the service, and traffic isn't forwarded to the pod instance.
+- One possible reason for a node entering a "Not Ready" state is the unavailability of the API server, which causes the readiness probe to fail. This failure prevents the pod from being attached to the service, resulting in traffic not being forwarded to the pod instance.
 
 - Virtual machine (VM) host faults occur. To determine whether VM host faults occurred, check the following information sources:
   - [AKS diagnostics](/azure/aks/concepts-diagnostics)
   - [Azure status](https://status.azure.com/)
   - Azure notifications (for any recent outages or maintenance periods)
 
+## Resolution
+
+Check the API server availability by running the following command: kubectl get apiservices.
+
+Ensure that the readiness probe is correctly configured in the deployment YAML file.
+
+For further steps check here: [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).
+
 ## Prevention
 
 To prevent this issue from occurring in the future, take one or more of the following actions:
 
 - Make sure that your service tier is fully paid for.
 - Reduce the number of `watch` and `get` requests to the API server.
-- Replace the node pool with a healthy node pool.
-
-## More information
-
-- For general troubleshooting steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).