-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-3695: Add updates around e2e tests #5430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Swati Gupta <swatig@nvidia.com>
Hi @guptaNswati. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/retitle KEP-3695: Add updates around e2e tests |
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the followup!
Other improvements are addressed in: | ||
- https://github.com/kubernetes/kubernetes/pull/132028 | ||
- https://github.com/kubernetes/kubernetes/pull/132345 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, but please doublecheck, is better not to link PRs in the KEP but rather describe the goal these PR implement.
The List
fix I mentioned previously is meant to illustrate
- the very case we missed
- the problem with API underspecification - which we kinda have for
Get
.
So I'd just remove lines 270-272
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets do that once these PRs are merged as @soltysh suggested.
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: | ||
- https://github.com/kubernetes/kubernetes/blob/v1.34.0-alpha.1/test/e2e_node/podresources_test.go#L977 | ||
- https://github.com/kubernetes/kubernetes/blob/v1.34.0-alpha.1/test/e2e_node/podresources_test.go#L1066 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...and we should rectify that and have this test clear and explicit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few nits, but overall this is good - thank you!
@@ -265,6 +265,12 @@ These cases will be added in the existing e2e tests: | |||
- Get API work with DRA and device plugin. | |||
- List API work with DRA and Device plugin. | |||
|
|||
[Get](https://github.com/kubernetes/kubernetes/pull/116846): [sig-node-kubelet](https://testgrid.k8s.io/sig-node-kubelet?include-filter-by-regex=PodResources), [triage](https://storage.googleapis.com/k8s-triage/index.html?test=PodResources) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR link should be replaced with actual code links to https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/podresources_test.go
|
||
Other improvements are addressed in: | ||
- https://github.com/kubernetes/kubernetes/pull/132028 | ||
- https://github.com/kubernetes/kubernetes/pull/132345 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those are fine, since those are no-merged PRs, so when updating this the next time you'll be able to replace these with appropriate links and descriptions like above.
@@ -334,7 +347,9 @@ The API becomes available again. The API is stateless, so no recovery is needed, | |||
|
|||
###### Are there any tests for feature enablement/disablement? | |||
|
|||
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) | |||
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, replace the PR link with code pointers to https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/podresources_test.go
@mrunalp can we get an approval on this update PR? It is a follow-up to what was merged before the KEP freeze. |
2ab1e07
to
59c48b3
Compare
@@ -282,6 +288,13 @@ These cases will be added in the existing e2e tests: | |||
|
|||
- [ ] Allowing time for feedback (1 year). | |||
- [ ] Risks have been addressed. | |||
- [ ] Add explicit feature enablement/disablement tests, before the feature is turned on by default. | |||
- [ ] Additional test cases are needed to verify Get() behavior in diverse scenarios |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where these addressed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the feature gate one: kubernetes/kubernetes#132827
@@ -282,6 +288,13 @@ These cases will be added in the existing e2e tests: | |||
|
|||
- [ ] Allowing time for feedback (1 year). | |||
- [ ] Risks have been addressed. | |||
- [ ] Add explicit feature enablement/disablement tests, before the feature is turned on by default. | |||
- [ ] Additional test cases are needed to verify Get() behavior in diverse scenarios | |||
- Pods with multiple containers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tests missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can be left out/last. I'm working on a PR to add it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding was to wait for this to be merged before adding other tests kubernetes/kubernetes#132028
- [ ] Add explicit feature enablement/disablement tests, before the feature is turned on by default. | ||
- [ ] Additional test cases are needed to verify Get() behavior in diverse scenarios | ||
- Pods with multiple containers. | ||
- Pods that do not use any exclusive resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, test already present. Stretch goal: add more coverage
- [ ] Additional test cases are needed to verify Get() behavior in diverse scenarios | ||
- Pods with multiple containers. | ||
- Pods that do not use any exclusive resources. | ||
- Comparison of List() and Get() on returned pods to validate consistency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test missing
- Pods with multiple containers. | ||
- Pods that do not use any exclusive resources. | ||
- Comparison of List() and Get() on returned pods to validate consistency. | ||
- Pod exists but container name is invalid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correction: turns out we have an existing test that roughly covers this use case
- Pods that do not use any exclusive resources. | ||
- Comparison of List() and Get() on returned pods to validate consistency. | ||
- Pod exists but container name is invalid | ||
- Get() is called on terminated pods to validate appropriate error handling. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test missing
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: guptaNswati, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
One-line PR description: Update KEP 3695 to address comments in PR kep-3695-beta update #5346
Issue link: DRA: Extend PodResources to include resources from Dynamic Resource Allocation #3695
/wg device-management
/assign @ffromani
/assign @soltysh
/assign @klueska