Skip to content

Commit 518e553

Browse files
csplintereasymrgr
authored andcommitted
1 parent df4633b commit 518e553

2 files changed

Lines changed: 8 additions & 2 deletions

File tree

latest/ug/nodes/node-health-nma.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -591,7 +591,7 @@ When you deploy the EKS node monitoring agent as an EKS add-on, you can customiz
591591

592592
|===
593593

594-
You can use the following AWS CLI commands to get useful information about the versions and schema for the EKS node monitoring agent EKS add-on.
594+
You can use the following {AWS} CLI commands to get useful information about the versions and schema for the EKS node monitoring agent EKS add-on.
595595

596596
Get the latest agent add-on version for your Kubernetes version. Replace `1.35` with your Kubernetes version.
597597

latest/ug/nodes/node-health.adoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Use the EKS node monitoring agent to detect health issues and EKS node repair to
1212

1313
Node health refers to the operational status and capability of a Kubernetes node to effectively run workloads. A healthy node maintains expected network connectivity, has sufficient compute and storage resources, and can successfully run workloads without disruption.
1414

15-
To help with maintaining healthy nodes in EKS clusters, EKS offers the _node monitoring agent_ and _automatic node repair_. These features are automatically enabled with EKS Auto Mode compute. You can also use automatic node repair with EKS managed node groups and Karpenter, and can use the EKS node monitoring agent with any EKS compute types except for AWS Fargate. The EKS node monitoring agent and automatic node repair are most effective when used together, but they can also be used individually in EKS clusters.
15+
To help with maintaining healthy nodes in EKS clusters, EKS offers the _node monitoring agent_ and _automatic node repair_. These features are automatically enabled with EKS Auto Mode compute. You can also use automatic node repair with EKS managed node groups and Karpenter, and can use the EKS node monitoring agent with any EKS compute types except for {AWS} Fargate. The EKS node monitoring agent and automatic node repair are most effective when used together, but they can also be used individually in EKS clusters.
1616

1717
[IMPORTANT]
1818
====
@@ -71,7 +71,13 @@ EKS automatic node repair does not react to standard Kubernetes `DiskPressure`,
7171

7272
For more information on EKS automatic node repair, see <<node-repair>>.
7373

74+
[.topiclist]
75+
[[Topic List]]
76+
7477
include::node-health-nma.adoc[leveloffset=+1]
78+
7579
include::node-repair.adoc[leveloffset=+1]
80+
7681
include::learn-status-conditions.adoc[leveloffset=+1]
82+
7783
include::auto-get-logs.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)