Skip to content

Commit df4633b

Browse files
csplintereasymrgr
authored andcommitted
Improvements to EKS NMA and node repair docs
cr: https://code.amazon.com/reviews/CR-254939183
1 parent 00e3293 commit df4633b

4 files changed

Lines changed: 841 additions & 471 deletions

File tree

latest/ug/nodes/learn-status-conditions.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This topic explains the tools and methods available for monitoring node health s
1212

1313
This topic explains the tools and methods available for monitoring node health status in Amazon EKS clusters. The information covers node conditions, events, and detection cases that help you identify and diagnose node-level issues. Use the commands and patterns described here to inspect node health resources, interpret status conditions, and analyze node events for operational troubleshooting.
1414

15-
You can get some node health information with Kubernetes commands for all nodes. And if you use the node monitoring agent through Amazon EKS Auto Mode or the Amazon EKS managed add-on, you will get a wider variety of node signals to help troubleshoot. Descriptions of detected health issues by the node monitoring agent are also made available in the observability dashboard. For more information, see <<node-health>>.
15+
You can get some node health information with Kubernetes commands for all nodes. And if you use the node monitoring agent through Amazon EKS Auto Mode or the Amazon EKS managed add-on, you will get a wider variety of node signals to help troubleshoot. Descriptions of detected health issues by the node monitoring agent are also made available in the observability dashboard. For more information, see <<node-health-nma>>.
1616

1717
[#status-node-conditions]
1818
== Node conditions

0 commit comments

Comments
 (0)