Skip to content

Commit f3a88db

Browse files
Update keps/sig-node/4680-add-resource-health-to-pod-status/README.md
Co-authored-by: John Belamaric <[email protected]>
1 parent b10035f commit f3a88db

File tree

1 file changed

+1
-1
lines changed
  • keps/sig-node/4680-add-resource-health-to-pod-status

1 file changed

+1
-1
lines changed

keps/sig-node/4680-add-resource-health-to-pod-status/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Device Plugin and DRA do not have a good failure handling strategy defined. With
7777

7878
Today, the typical design is for jobs consuming a failing device to fail with a specific error code whenever possible. For long running workloads, K8s will keep restarting the workload without reallocating it on a different device. So the container will be in crash loop backoff with limited information on why it is crashing.
7979

80-
People develop strategies to deal with such situations. Exposing unhealthy devices in Pod Status will provide a generic way to understand that the failure is related to the unhealthy device and be able to respond to this properly.
80+
Exposing unhealthy devices in Pod Status will provide a generic way to understand that the failure is related to the unhealthy device, and be able to respond to this properly.
8181

8282
### Goals
8383

0 commit comments

Comments
 (0)