AWS eks: Node health NMA: clarify Reboot vs Replace repair actions
Summary
Replaces curly quotes with straight quotes around "Condition" in several monitoring-condition sentences, and adds a note (twice) that the Reboot repair action only applies to EKS Managed Node Groups, while EKS Auto Mode and Karpenter only support Replace.
Security assessment
The only substantive content change clarifies node repair behavior (Reboot vs Replace) for different node management modes; the rest is quote-character normalization. This affects operational availability/remediation, not access control, encryption, credentials, or exposure.
Evidence
+The monitoring condition is `AcceleratedHardwareReady` for issues in the following table that have a severity of "Condition". The events and conditions in the following table are for NVIDIA and Neuron related node health issues. The Reboot repair action only applies to EKS Managed Node Groups. When using EKS Auto Mode or Karpenter, the only repair action is Replace.
Diff
diff --git a/eks/latest/userguide/node-health-nma.md b/eks/latest/userguide/node-health-nma.md index e5d20503c..d326c63bd 100644 --- a//eks/latest/userguide/node-health-nma.md +++ b//eks/latest/userguide/node-health-nma.md @@ -34 +34 @@ The following tables describe node health issues that can be detected by the nod -The monitoring condition is `AcceleratedHardwareReady` for issues in the following table that have a severity of “Condition”. The events and conditions in the following table are for NVIDIA and Neuron related node health issues. +The monitoring condition is `AcceleratedHardwareReady` for issues in the following table that have a severity of "Condition". The events and conditions in the following table are for NVIDIA and Neuron related node health issues. The Reboot repair action only applies to EKS Managed Node Groups. When using EKS Auto Mode or Karpenter, the only repair action is Replace. @@ -71 +71 @@ For more information on XID errors, see [Xid Errors](https://docs.nvidia.com/dep -The following table lists the well-known XID codes, their meanings, and the default node repair action if enabled. +The following table lists the well-known XID codes, their meanings, and the default node repair action if enabled. The Reboot repair action only applies to EKS Managed Node Groups. When using EKS Auto Mode or Karpenter, the only repair action is Replace. @@ -109 +109 @@ To view XID-related events on your cluster, run one of the following commands. -The monitoring condition is `ContainerRuntimeReady` for issues in the following table that have a severity of “Condition”. +The monitoring condition is `ContainerRuntimeReady` for issues in the following table that have a severity of "Condition". @@ -124 +124 @@ ServiceFailedToStart | Event | A systemd unit failed to start. | None -The monitoring condition is `KernelReady` for issues in the following table that have a severity of “Condition”. +The monitoring condition is `KernelReady` for issues in the following table that have a severity of "Condition". @@ -142 +142 @@ SoftLockup | Event | The CPU stalled for a given amount of time. | None -The monitoring condition is `NetworkingReady` for issues in the following table that have a severity of “Condition”. +The monitoring condition is `NetworkingReady` for issues in the following table that have a severity of "Condition". @@ -171 +171 @@ UnexpectedRejectRule | Event | An unexpected `REJECT` or `DROP` rule was found -The monitoring condition is `StorageReady` for issues in the following table that have a severity of “Condition”. +The monitoring condition is `StorageReady` for issues in the following table that have a severity of "Condition".