You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -282,6 +288,13 @@ These cases will be added in the existing e2e tests:
282
288
283
289
-[ ] Allowing time for feedback (1 year).
284
290
-[ ] Risks have been addressed.
291
+
-[ ] Add explicit feature enablement/disablement tests, before the feature is turned on by default.
292
+
-[ ] Additional test cases are needed to verify Get() behavior in diverse scenarios
293
+
- Pods with multiple containers.
294
+
- Pods that do not use any exclusive resources.
295
+
- Comparison of List() and Get() on returned pods to validate consistency.
296
+
- Pod exists but container name is invalid
297
+
- Get() is called on terminated pods to validate appropriate error handling.
285
298
286
299
### Upgrade / Downgrade Strategy
287
300
@@ -334,7 +347,9 @@ The API becomes available again. The API is stateless, so no recovery is needed,
334
347
335
348
###### Are there any tests for feature enablement/disablement?
336
349
337
-
e2e test will demonstrate that when the feature gate is disabled, the API returns the appropriate error code. (https://github.com/kubernetes/kubernetes/pull/116846)
350
+
This e2e test (https://github.com/kubernetes/kubernetes/pull/116846) will demonstrate that when the feature gate is disabled, the API returns the appropriate error code. The explicit on/off tests are scattered across the existing tests:
0 commit comments