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

Add CDI devices to device plugin API #4009

Open
9 of 13 tasks
klueska opened this issue May 15, 2023 · 30 comments
Open
9 of 13 tasks

Add CDI devices to device plugin API #4009

klueska opened this issue May 15, 2023 · 30 comments
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Milestone

Comments

@klueska
Copy link
Contributor

klueska commented May 15, 2023

Enhancement Description

@SergeyKanzhelev
Copy link
Member

/milestone v1.28

@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone May 26, 2023
@SergeyKanzhelev
Copy link
Member

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jun 6, 2023
@SergeyKanzhelev
Copy link
Member

/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Jun 8, 2023
@npolshakova
Copy link

Hi @klueska 👋, 1.28 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023.

This enhancement is targeting for stage alpha for 1.28 (correct me, if otherwise.)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.28
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

It looks like #4011 will address most of these issues

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@npolshakova
Copy link

Hi @klueska, checking in once more as we approach the 1.28 enhancement freeze deadline on 01:00 UTC Friday, 16th June 2023. The status of this enhancement is marked as at risk. It looks like #4011 will address most of the requirements. Let me know if I missed anything. Thanks!

@klueska
Copy link
Contributor Author

klueska commented Jun 16, 2023

@npolshakova #4011 has been merged

@Atharva-Shinde
Copy link
Contributor

Hey @klueska
With all the KEP requirements in place and merged into k/enhancements, the status of this enhancement is now marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

@VibhorChinda
Copy link

Hello @klueska 👋, 1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@npolshakova
Copy link

Hey again @klueska 👋

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

  • All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
  • All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

For this enhancement, it looks like the following code related PR/s are open and they need to be merged or should be in merge-ready state before the code freeze commences :

Also please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

@Rishit-dagli
Copy link
Member

Hey @klueska , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.

@klueska
Copy link
Contributor Author

klueska commented Jul 12, 2023

/cc @elezar who is working on this feature

@elezar
Copy link
Contributor

elezar commented Jul 12, 2023

I have created a draft PR: kubernetes/website#42001

@Atharva-Shinde
Copy link
Contributor

Hey @klueska 👋 Enhancements Lead here,
With kubernetes/kubernetes#118254 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze. Thanks!

@Rishit-dagli
Copy link
Member

Hello @klueska @elezar wave: please take a look at Documenting for a release - PR Ready for Review to get your docs PR ready for review before Tuesday 25th July 2023. Thank you!

Ref: kubernetes/website#42001

@npolshakova
Copy link

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Aug 27, 2023
@klueska
Copy link
Contributor Author

klueska commented Sep 25, 2023

I have added a KEP update link to this issue, to transition this feature to beta in 1.29

@npolshakova
Copy link

Hello @klueska, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

@bart0sh
Copy link
Contributor

bart0sh commented Oct 3, 2023

@mrunalp @SergeyKanzhelev Can you add lead-opted-in label to this issue, please? The issue was included into the SIG-Node 1.29 planning document long time ago.

@bart0sh
Copy link
Contributor

bart0sh commented Oct 3, 2023

@mrunalp @SergeyKanzhelev can you also change milestone to 1.29 ?

@SergeyKanzhelev
Copy link
Member

/milestone v1.29

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.28, v1.29 Oct 3, 2023
@SergeyKanzhelev
Copy link
Member

/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Oct 3, 2023
@sanchita-07
Copy link
Member

sanchita-07 commented Oct 4, 2023

Hello @klueska 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage beta for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.29.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, it looks like merging of #4238 will be good to go for marking the KEP as tracked for enhancement freeze.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

Thank you!

@sanchita-07
Copy link
Member

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze 🚀.
The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.
Thank You!

@Princesso
Copy link

Hey there @klueska ! 👋, v1.29 Docs team shadow here.
Does this enhancement work planned for v1.29 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.
Thank you!

@bart0sh
Copy link
Contributor

bart0sh commented Oct 11, 2023

@Princesso done: kubernetes/website#43435

@sanchita-07
Copy link
Member

Hey again @klueska 👋, 1.29 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023:

Here's where this enhancement currently stands:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Please update the Issue description to include all the related PRs of this KEP. The status for this KEP is currently at risk for code freeze.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

As always, we are here to help if any questions come up ✌. Thanks :)

@elezar
Copy link
Contributor

elezar commented Oct 30, 2023

@klueska the code changes for this are in kubernetes/kubernetes#121440 could you update the description?

@kcmartin
Copy link

Hi @klueska , 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here is the 1.29 calendar

@sanchita-07
Copy link
Member

Hello @klueska 👋, 1.29 Enhancements team here.

Making sure are the following PRs related to the current KEP?
With all the following implementation(code related) PRs merged into k/k, this enhancement is now marked as tracked for code freeze for the 1.29 Code Freeze! 🚀
Are there any other PRs other than the following ones? If there are any other PRs that need to be tracked, please let us know. Also please update the issue description with the following PR:

The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then. The tracked test PR for this KEP is:

Please let me know if there are additional test PRs we should track. Thanks!

@bart0sh
Copy link
Contributor

bart0sh commented Nov 6, 2023

@sanchita-07 Your PR list looks correct. Both PRs have been already merged.
There is also one documentation PR. It's pending approval atm: kubernetes/website#43435

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
Status: Tracked
Status: Tracked for Code Freeze
Development

No branches or pull requests