-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CDI for device plugins: update test grid and triage links #4521
CDI for device plugins: update test grid and triage links #4521
Conversation
@@ -157,10 +157,10 @@ This test case has been added to the existing `e2e_node` tests: | |||
- DevicePlugin can make a CDI device accessible in a container | |||
|
|||
Links to test grid: | |||
- https://testgrid.k8s.io/sig-node-containerd#e2e-cos-device-plugin-gpu |
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 change was because we got rid of this job and we are replacing it with the crio job?
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 because we now have a job that runs only CDI-related tests, so these links are more appropriate in this KEP in my opinion.
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 main point about bringing up crio was making sure we had both crio and containerd coverage for GA. Do we have containerd tests for this feature still?
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.
No, we don't. I was planning to enable CDI tests for containerd 2.0, where CDI is enabled by default. However, I can create a Containerd job similar to the CRI-O one if needed.
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.
So what kind of guards do you have in place that this wouldn't break in containerd without these tests? If its covered somewhere I guess its fine.
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.
It's partly covered by DRA e2e as it also depends on CDI.
/lgtm |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/remove-lifecycle stale |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bart0sh, 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: CDI for device plugins: update test grid and triage links
Issue link: Add CDI devices to device plugin API #4009
Other comments: New test infra job has been created to test CDI support for device plugins to make sure other tests will not influence graduation of this feature to GA. This PR updates test grid and triage links to point to the new job.