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

Graduate to CPUManager to GA #3570

Open
4 tasks done
fromanirh opened this issue Sep 30, 2022 · 14 comments
Open
4 tasks done

Graduate to CPUManager to GA #3570

fromanirh opened this issue Sep 30, 2022 · 14 comments
Assignees
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/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@fromanirh
Copy link
Contributor

fromanirh commented Sep 30, 2022

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

The original issue (#375) is closed and missed the proper labeling. Fixing with this one.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 30, 2022
@fromanirh
Copy link
Contributor Author

fromanirh commented Sep 30, 2022

CPU Manager is consumed by multiple parties and trated as GA. We want to avoid the perma-beta status

@fromanirh
Copy link
Contributor Author

fromanirh commented Sep 30, 2022

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 30, 2022
@dims
Copy link
Member

dims commented Sep 30, 2022

/label lead-opted-in
/milestone v1.26

@derekwaynecarr @dchen1107 @SergeyKanzhelev adding labels based on request on slack thread - https://kubernetes.slack.com/archives/C0BP8PW9G/p1664537014576579

please clear them if it is not appropriate.

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 30, 2022
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 30, 2022
@rhockenbury
Copy link

rhockenbury commented Sep 30, 2022

/label tracked/yes
/stage stable

@k8s-ci-robot k8s-ci-robot added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 30, 2022
@derekwaynecarr
Copy link
Member

derekwaynecarr commented Oct 3, 2022

/label lead-opt-in

volunteer identified in sig to see this to stable in sig-node.

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Oct 3, 2022

@derekwaynecarr: The label(s) `/label lead-opt-in

cannot be applied. These labels are supported:api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes`

In response to this:

/label lead-opt-in

volunteer identified in sig to see this to stable in sig-node.

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.

@derekwaynecarr
Copy link
Member

derekwaynecarr commented Oct 3, 2022

/label lead-opted-in

@ruheenaansari34
Copy link

ruheenaansari34 commented Oct 4, 2022

Hello @fromanirh 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage stable for 1.26 (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.26
  • 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.

For this KEP, we would just need to update:

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!

@rhockenbury
Copy link

rhockenbury commented Oct 7, 2022

With #3350 merged, this is tracked for v1.26

@sftim
Copy link
Contributor

sftim commented Oct 10, 2022

I recommend cracking on with early work on a docs update so that these are GA quality (or have PRs open to make them be) by the appropriate review deadline.

@dims
Copy link
Member

dims commented Oct 19, 2022

Reflects the KEP update already merged:
https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3570-cpumanager/kep.yaml#L35-L38

/approve
/lgtm

fromanirh added a commit to fromanirh/website that referenced this issue Oct 21, 2022
Assuming that the feature goes into 1.26 as GA, this will
become a blog post about it.

Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
@Atharva-Shinde
Copy link

Atharva-Shinde commented Oct 31, 2022

Hey @fromanirh 👋,

Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

As always, we are here to help should questions come up.
Thanks :)

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

With those PRs merged, we have this marked as tracked for code freeze.

@krol3
Copy link

krol3 commented Nov 9, 2022

Hello @fromanirh 👋, 1.26 Release Docs Lead here. This enhancement is marked as ‘Needs Docs’ for 1.26 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Any doubt, reach us! Thank you!

fromanirh added a commit to fromanirh/website that referenced this issue Nov 21, 2022
Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
fromanirh added a commit to fromanirh/website that referenced this issue Nov 25, 2022
Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
fromanirh added a commit to fromanirh/website that referenced this issue Nov 28, 2022
Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
fromanirh added a commit to fromanirh/website that referenced this issue Nov 28, 2022
Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
fromanirh added a commit to fromanirh/website that referenced this issue Nov 29, 2022
Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
fromanirh added a commit to fromanirh/website that referenced this issue Nov 29, 2022
Enhancement: kubernetes/enhancements#3570

Signed-off-by: Francesco Romani <fromani@redhat.com>
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/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Graduating
Development

No branches or pull requests

9 participants