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

Topology Manager for 1.17 Tracking Issue #83479

Closed
klueska opened this issue Oct 3, 2019 · 12 comments
Closed

Topology Manager for 1.17 Tracking Issue #83479

klueska opened this issue Oct 3, 2019 · 12 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@klueska
Copy link
Contributor

klueska commented Oct 3, 2019

This issue is used to track the enhancements we plan to make to the TopologyManager in the 1.17 timeframe.

The tracking issue for the full TopologyManager feature can be found here:
kubernetes/enhancements#693

The following PRs track each of the 1.17 enhancements individually:

Bug Fixes:
#84525 Fix bug in TopologyManager hint generation after kubelet restart
#83777 Fixed bug in TopologyManager with SingleNUMANode Policy
#82104 Fix bug in CPUManager with setting topology for policies
#83196 using online file instead to fix NUMA nodes init

Features:
#83043 Delegate topology hint gen to CPU manager policy
#83033 Rename package socketmask to bitmask.
#83492 Topology manager aligns pods of all QoS classes.
#84721 Base Infrastructure for adding Merge() API to TopologyManager Policies

Documentation:
kubernetes/website#17451 Topology management doc updates

@klueska klueska added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 3, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Oct 3, 2019
@klueska
Copy link
Contributor Author

klueska commented Oct 3, 2019

/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 Oct 3, 2019
@derekwaynecarr
Copy link
Member

/milestone v1.17

@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone Oct 3, 2019
@ConnorDoyle
Copy link
Contributor

/cc

@lmdaly
Copy link
Contributor

lmdaly commented Oct 16, 2019

/cc

@josiahbjorgaard
Copy link
Contributor

josiahbjorgaard commented Oct 26, 2019

Bug triage for release 1.17 here. Since this issue has been tagged for the milestone, we would like to check it's status. Code freeze is on Nov. 14. Will this issue be resolved before then? If not, we should move it out of the milestone.

@josiahbjorgaard
Copy link
Contributor

Hi bug triage team for 1.17, will this issue be resolved before code freeze on Nov. 14 (next Thursday)?

@klueska
Copy link
Contributor Author

klueska commented Nov 4, 2019

@josiahbjorgaard We are still pushing for it, but it's definitely at risk of not making it

/cc @ConnorDoyle
/cc @derekwaynecarr
/cc @lmdaly

@klueska
Copy link
Contributor Author

klueska commented Nov 11, 2019

I have updated the description for this issue to only include the PRs we actually plan on getting into 1.17 at this point. The only remaining PR is the documentation one from @lmdaly. All others have been merged already.

Unfinished work has been pushed out to a tracking issue for 1.18: #85093

@josiahbjorgaard
Copy link
Contributor

@klueska Will you please make sure to close the issue once all v1.17 is complete?

@josiahbjorgaard
Copy link
Contributor

/milestone clear

(v1.17 code freeze)

@k8s-ci-robot k8s-ci-robot removed this from the v1.17 milestone Nov 15, 2019
@lmdaly
Copy link
Contributor

lmdaly commented Nov 22, 2019

kubernetes/website#17451 is now merged

@klueska
Copy link
Contributor Author

klueska commented Nov 22, 2019

All PRs tracked by this issue have now been merged. Closing

@klueska klueska closed this as completed Nov 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

6 participants