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
Support 3rd party device monitoring plugins #606
Comments
@dashpole this has been added to the 1.12 tracking sheet. Thank you @justaugustus please add relevant tags to this issue |
@kacole2 all set! |
@dashpole looks like design proposal link should be this one: https://docs.google.com/document/d/1NYnqw-HDQ6Y3L_mk85Q3wkxDtGNWTxpsedsgw4NgWpg/edit |
Agreed, that makes more sense |
/assign @dashpole |
Hey there! @dashpole I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it? |
@zparnold here is the docs pr placeholder: kubernetes/website#9945 |
Thank you @dashpole! |
@dashpole -- |
It can be removed from the milestone |
Got it. Thanks for the update! |
Hi @dashpole Please take a moment to ping @kacole2 so it can be included in the 1.13 Enhancements Tracking Sheet if it's going to make it. Thanks! |
/milestone v1.13 |
@dashpole could you please let us know whats pending for this feature to go to Alpha in 1.13. Do you have a list of pending PRs or issues you can point us to. Thanks |
@dashpole there has been no communication on the status. Are we confident this is going to make the v1.13 milestone? Enhancement freeze is tomorrow COB. If there is no communication or update on the PR, this is going to be pulled from the milestone as it doesn't fit with our "stability" theme. If there is no communication after COB tomorrow, an exception will be required to add it back to the milestone. Please let me know where we stand. Thanks! |
KEP: kubernetes/community#2454 should be merged soon, as it is approved by the required people. Once that happens, Ill open the implementation PR, and get working on docs. I still expect this to land in 1.13. |
@ffromani: Reopened this issue. In response to this:
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/test-infra repository. |
/milestone v1.27 @ffromani I think you still plan to make it happen, correct? |
Hello @ffromani Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this enhancement, it looks like #3791 will address the remaining requirements. The status of this enhancement is marked as |
This enhancement meets all the requirements to be included in v1.27 and is now tracked for the release. Thanks @ffromani! |
Hi @dashpole Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. |
Hi @dashpole
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze: Please let me know what other PRs in k/k I should be tracking for this KEP. |
Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release. If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md /milestone clear |
no problem. Deferring to 1.28 is not a big deal. We made good progress on GA blockers. I'll be working to merge kubernetes/kubernetes#115133 as early as possible and we should have a much easier path to GA this work in 1.28. |
/milestone v1.28 |
/lead-opted-in |
/label lead-opted-in |
Hello @ffromani @dashpole Just checking in as we approach enhancements freeze on Thursday, 16th June 2023. Looks like this enhancement is Here's where this enhancement currently stands:
For this KEP, we would simply need to update the following:
The status of this enhancement is marked as |
Hi @Atharva-Shinde , thanks for reaching out. The latest pending item for this work, which slipped in 1.28, was actually moving all the FGs to locked (kubernetes/kubernetes#116525). The PRR for GA stage was already passed: #3791 (comment) |
Feature Description
One-line feature description (can be used as a release note): Support 3rd party device monitoring plugins
Primary contact (assignee): @ffromani
Responsible SIGs: sig-node
Design proposal link (community repo): KEP: Support Device Monitoring community#2454
KEP: 606-compute-device-assignment
Link to e2e and/or unit tests: Coming Soon
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @vikaschoudhary16 @jiayingz
Approver (likely from SIG/area to which feature belongs): @derekwaynecarr
Feature target (which target equals to which milestone):
Stable
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):/kind feature
/sig node
The text was updated successfully, but these errors were encountered: