DRA E2E: run some tests without feature label #131956
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/test pull-kubernetes-e2e-kind-dra |
|
/test pull-kubernetes-kind-dra |
|
The "control plane" tests currently fail to tear down pods because of #131957. |
7f49575 to
df51936
Compare
|
/test pull-kubernetes-kind-dra |
df51936 to
df8500f
Compare
|
/test pull-kubernetes-kind-dra |
|
/triage accepted |
|
/assign @pohly feel free to ping for the review once it is ready. |
1e87a7f to
c3079cf
Compare
|
[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 |
|
/test pull-kubernetes-kind-dra |
pohly
added a commit
to pohly/kubernetes
that referenced
this pull request
Jun 26, 2025
c3079cf to
d6539ff
Compare
|
/test pull-kubernetes-kind-dra |
pohly
added a commit
to pohly/kubernetes
that referenced
this pull request
Jun 27, 2025
|
@harche: this is ready for review and merging. pull-kubernetes-e2e-kind-beta-features includes the tests that can run without kubelet (search for |
e0552fd to
66a1afb
Compare
Tests which only exercise the control plane don't need DRA drivers on the nodes and thus can run in any cluster where the API and feature gate is enabled. Eventually they can become conformance tests. The actual test cases follow the same pattern and in some cases are run twice, once for "control plane" testing and once for "kubelet" testing. The difference is that in "control plane" mode, the driver's don't get deployed and pods are only expected to get scheduled instead of starting to run.
66a1afb to
00dd610
Compare
|
/assign @bart0sh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Tests which only exercise the control plane don't need DRA drivers on the nodes and thus can run in any cluster where the API and feature gate is enabled. Eventually they can become conformance tests.
Which issue(s) this PR fixes (or partially fixes):
#114183
Special notes for your reviewer:
The actual test cases follow the same pattern and in some cases are run twice, once for "control plane" testing and once for "kubelet" testing. The difference is that in "control plane" mode, the driver's don't get deployed and pods are only expected to get scheduled instead of starting to run.
Does this PR introduce a user-facing change?