-
Notifications
You must be signed in to change notification settings - Fork 41.1k
DRA E2E cleanup #133141
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
DRA E2E cleanup #133141
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
"must be possible for the driver to update the ResourceClaim.Status.Devices once allocated" was also run as kubelet test although it only checks the control plane. Before: [sig-node] [DRA] [FeatureGate:DynamicResourceAllocation] [Beta] [Feature:OffByDefault] control plane with single node [ConformanceCandidate] must be possible for the driver to update the ResourceClaim.Status.Devices once allocated [FeatureGate:DRAResourceClaimDeviceStatus] [Beta] [sig-node] [DRA] [FeatureGate:DynamicResourceAllocation] [Beta] [Feature:OffByDefault] kubelet [Feature:DynamicResourceAllocation] on single node must be possible for the driver to update the ResourceClaim.Status.Devices once allocated [FeatureGate:DRAResourceClaimDeviceStatus] [Beta] After: [sig-node] [DRA] [FeatureGate:DynamicResourceAllocation] [Beta] [Feature:OffByDefault] control plane with single node [ConformanceCandidate] must be possible for the driver to update the ResourceClaim.Status.Devices once allocated [FeatureGate:DRAResourceClaimDeviceStatus] [Beta]
There's no need to clarify how many nodes are used in the test because the overall test names are still unique without that (verified with go test -v ./test/e2e -args -list-tests | grep -w DRA | wc -l).
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly 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 |
The tests should work also with only two nodes, which is the minimum required for conformance testing.
/lgtm |
/lgtm /hold if you want to wait for Ed, otherwise unhold |
LGTM label has been added. Git tree hash: b9896f84f1a55b6e963d132b6481c29177d87f33
|
jinx /hold cancel sorry |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR is related to:
#133132 (comment)
Does this PR introduce a user-facing change?
/assign @bart0sh
/priority critical-urgent