Add CPU Manager for pod cpuset assignment

[sjenning]

Feature Description

• One-line feature description (can be used as a release note): add CPU Manager for pod cpuset assignment based on resource/QoS attributes
• Primary contact (assignee): @sjenning, @ConnorDoyle
• Responsible SIGs: sig-node
• Design proposal link (community repo): Add CPU manager proposal. community#654
• Reviewer(s) - (for LGTM) @derekwaynecarr @vishh
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone): alpha 1.8

Add UpdateContainerResources method to CRI:
kubernetes/kubernetes#46105

Primary feature PR:
kubernetes/kubernetes#49186

[jdumars]

/sig node

[ConnorDoyle]

@dchen1107 or @vishh -- could one of you add the v1.8 milestone?

[ConnorDoyle]

Also the stage/alpha label please.

[ConnorDoyle]

/assign @sjenning
/assign @ConnorDoyle

[idvoretskyi]

@sjenning @kubernetes/sig-cluster-lifecycle-feature-requests any updates for 1.8? Is this feature still on track for the release?

[ConnorDoyle]

Yes, the alpha version of the feature merged over the weekend, examples and node e2e are in review.

[ConnorDoyle]

We are targeting v1.9 to graduate this feature from alpha to beta.

[adohe-zz]

@ConnorDoyle as what we talk on Slack, is there anything I can help?

[pires]

Was this in fact graduated to beta in 1.9?

[idvoretskyi]

@pires no, this feature hasn't been announced as beta in 1.9.

[justaugustus]

@ConnorDoyle @sjenning
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[justaugustus]

This feature current has no milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that Features Freeze is tomorrow, July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

P.S. This was sent via automation

[kacole2]

Hi
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:

• Docs (open placeholder PRs): 11/8
• Code Slush: 11/9
• Code Freeze Begins: 11/15
• Docs Complete and Reviewed: 11/27

Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet

Thanks!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[mrbobbytables]

/remove-lifecycle stale

[claurence]

@sjenning, @ConnorDoyle Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP

[sjenning]

Didn't realize this was still hanging around. This went alpha in 1.9, which is what this issue is tracking. We can open a new issue to track beta promotion IIUC.

[sjenning]

I'm losing it. This went beta a long time ago kubernetes/kubernetes#55977

[ffromani]

I'm working to graduate this feature to GA in 1.26