@@ -151,6 +151,12 @@ However, these cases will be added in the existing integration tests:
151
151
These cases will be added in the existing ` e2e_node ` tests:
152
152
- Device Plugin works with CDI devices
153
153
154
+ Links to tests:
155
+ - TBD: Will fill-in by code freeze
156
+
157
+ Links to k8s-triage for tests:
158
+ - TBD: Will fill-in by code freeze
159
+
154
160
### Graduation Criteria
155
161
156
162
#### Alpha
315
321
316
322
### Troubleshooting
317
323
324
+ ###### How does this feature react if the API server and/or etcd is unavailable?
325
+
318
326
N/A
319
327
320
328
###### What are other known failure modes?
321
329
322
- TBD
330
+ The change to Kubernetes to support this feature is very minimal. The CDI
331
+ device list passed from the plugin to the kubelet is opaquely forwarded to the
332
+ underlying container runtime without affecting the overall logic of the kubelet
333
+ in any significant way. As such, the only known failure scenarios result from
334
+ plugins themselves doing something incorrectly (not the kubelet). For example,
335
+ sending back a list of CDI devices that are not included in any CDI spec
336
+ visible to the underlying container runtime. However, such failure scenarios do
337
+ not affect the proper functioning of kubernetes itself, and are therefore out
338
+ of scope for this KEP. We recommend you check the device plugin and container
339
+ runtime logs instead.
323
340
324
341
###### What steps should be taken if SLOs are not being met to determine the problem?
325
342
328
345
## Implementation History
329
346
330
347
- 2023-05-15: KEP created
348
+ - 2023-09-25: KEP updated to mark transition to beta
331
349
332
350
## Drawbacks
333
351
0 commit comments