Skip to content
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

Conversation

bart0sh
Copy link
Contributor

@bart0sh bart0sh commented Feb 15, 2024

  • 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.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 15, 2024
@k8s-ci-robot k8s-ci-robot added the kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory label Feb 15, 2024
@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 15, 2024
@bart0sh
Copy link
Contributor Author

bart0sh commented Feb 15, 2024

@@ -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
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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?

Copy link
Contributor Author

@bart0sh bart0sh Feb 15, 2024

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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.

@kannon92
Copy link
Contributor

/lgtm
/assign @SergeyKanzhelev @mrunalp @dchen1107

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 15, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 15, 2024
@bart0sh
Copy link
Contributor Author

bart0sh commented May 16, 2024

/remove-lifecycle stale
@mrunalp @SergeyKanzhelev @dchen1107 PTAL

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 16, 2024
@bart0sh
Copy link
Contributor Author

bart0sh commented May 18, 2024

/remove-lifecycle stale

Copy link
Contributor

@mrunalp mrunalp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 29, 2024
@k8s-ci-robot k8s-ci-robot merged commit 3fed55c into kubernetes:master May 29, 2024
2 of 4 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.31 milestone May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
Development

Successfully merging this pull request may close these issues.

7 participants