docs(k8s): autoheal

containers/kubernetes/reference-content/using-kubernetes-autoheal-feature.mdx

@@ -24,6 +24,10 @@ You can enable the autoheal feature to ensure that your applications remain oper
 - **Reduced downtime**: By automatically detecting and recovering from failures, autoheal reduces downtime and minimizes the impact on application performance.
 - **Operational efficiency**: It reduces the need for manual intervention in addressing failures, thereby improving operational efficiency.
 
+## Autoheal process
+
+Autoheal is triggered by the shoot-manager every five (5) minutes. If the shoot-manager sees a node in `notReady` status for more than 15 minutes, it will reboot it (once only), and after 30 minutes it will be replaced.
+
 ## When to enable or disable autoheal
 
 ### When to enable autoheal
@@ -37,15 +41,6 @@ There may be scenarios where autoheal should be disabled:
 - **Testing environments**: In testing or development environments where failures can be tolerated for troubleshooting purposes.
 - **Custom ranecovery mechanisms**: If custom recovery mechanisms are in place that handle failures more effectively than the autoheal feature.
 
-## Autoheal process
-
-When autoheal is triggered, it typically follows a process of replacing the affected components, such as:
-
-- **Node Replacement**: In the case of node failures, autoheal may initiate the replacement of the failed node.
-
-The Kubernetes autoheal feature provides a basic mechanism for maintaining the health and availability of applications running on Kubernetes clusters.
-By automatically detecting and recovering from failures, it helps ensure continuous operation and minimizes the impact of disruptions on application performance.
-
 <Message type="important">
     You are advised to carefully consider the implications of enabling or disabling autoheal based on your specific use case requirements and operational considerations.
-</Message>
+</Message>