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

Improved multi-numa alignment in Topology Manager #3545

Open
2 of 4 tasks
klueska opened this issue Sep 23, 2022 · 15 comments
Open
2 of 4 tasks

Improved multi-numa alignment in Topology Manager #3545

klueska opened this issue Sep 23, 2022 · 15 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/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@klueska
Copy link
Contributor

klueska commented Sep 23, 2022

Enhancement Description

@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Sep 23, 2022
@klueska klueska changed the title Improved multi-numa alignment in Topology Manage Improved multi-numa alignment in Topology Manager Sep 23, 2022
@klueska
Copy link
Contributor Author

klueska commented Sep 26, 2022

/cc @fromanirh
/cc @swatisehgal

@fromanirh
Copy link
Contributor

fromanirh commented Sep 26, 2022

thanks for the heads up, I'll review shortly

@derekwaynecarr
Copy link
Member

derekwaynecarr commented Sep 27, 2022

/label lead-opted-in

@derekwaynecarr derekwaynecarr added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 27, 2022
@Atharva-Shinde
Copy link

Atharva-Shinde commented Sep 28, 2022

Hey @klueska 👋, 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 alpha for 1.26

Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has an updated detailed test plan section filled out
  • KEP 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:
-Get the PR #3549 merged before Enhancements Freeze to make this enhancement eligible for 1.26 release.

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 :)

@Atharva-Shinde
Copy link

Atharva-Shinde commented Sep 28, 2022

/milestone v1.26
/label tracked/yes

@k8s-ci-robot k8s-ci-robot added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 28, 2022
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 28, 2022

@Atharva-Shinde: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.26
/label tracked/yes

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.

@Atharva-Shinde
Copy link

Atharva-Shinde commented Sep 28, 2022

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Sep 28, 2022
@rhockenbury rhockenbury added this to the v1.26 milestone Sep 29, 2022
@Atharva-Shinde
Copy link

Atharva-Shinde commented Oct 5, 2022

Hello @klueska 👋, just a quick check-in again, as we approach the 1.26 Enhancements freeze.

Please plan to get the action items mentioned in my comment above done before Enhancements freeze on 18:00 PDT on Thursday 6th October 2022 i.e tomorrow

For note, the current status of the enhancement is marked at-risk :)

@rhockenbury
Copy link

rhockenbury commented Oct 6, 2022

We have this marked as tracked for v1.26 with #3549 merged.

@Atharva-Shinde
Copy link

Atharva-Shinde commented Oct 31, 2022

Hi @klueska 👋,

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 :)

@Atharva-Shinde
Copy link

Atharva-Shinde commented Nov 7, 2022

Hey @klueska 👋, just a quick check-in again before 1.26 code freeze at 17:00 PDT Tuesday 8th November 2022 i.e tomorrow.
Looks like we would at least need to get the code PR/s: kubernetes/kubernetes#112914 (any more PRs?) merged before the code-freeze :)

@krol3
Copy link

krol3 commented Nov 7, 2022

Hello @klueska 👋, 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!

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

With kubernetes/kubernetes#112914 merged, we have this marked as tracked for code freeze.

@krol3
Copy link

krol3 commented Nov 11, 2022

Hello @klueska 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before deadline Tuesday 15th November 2022. Thank you!

@krol3
Copy link

krol3 commented Nov 14, 2022

Hi @klueska ! thank you for your doc PR here

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 tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Net New
Development

No branches or pull requests

7 participants