Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing

[jingczhang]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing

• Kubernetes Enhancement Proposal:
  https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4540-strict-cpu-reservation/README.md

• Discussion Link:
  Feature: Add StrictCPUReservation option in static cpu policy kubernetes#103933

• Primary contact (assignee):
  @jingczhang

• Responsible SIGs:
  /sig node

• Enhancement target (which target equals to which milestone):

  • Alpha release target (1.32):
  • Beta release target (1.33):
  • Stable release target (1.35):

• Alpha

  • KEP (k/enhancements) update PR(s): KEP-4540: Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing #4540 #4541
  • Code (k/k) update PR(s): KEP-4540: Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing kubernetes#127483 and node: metrics: add metrics about cpu pool sizes kubernetes#127506
  • Docs (k/website) update PR(s): KEP-4540: CPUManager strict-cpu-reservation policy option documentation website#48356 and KEP-4540: CPUManager strict-cpu-reservation policy option blog website#48371

• Beta

  • KEP (k/enhancements) update PR(s): KEP-4540: Move to beta #5128
  • Code (k/k) update PR(s): KEP-4540: strict-cpu-reservation beta kubernetes#130290
  • Docs (k/website) update(s): Mark strict-cpu-reservation as beta website#49902

• Stable

  • KEP (k/enhancements) update PR(s): KEP-4540: Promote the CPUManager Policy Option strict-cpu-reservation to GA #5587
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

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

[ffromani]

Hi, thanks for filing the issue. Unfortunately the 1.30 release is already in code freeze, so the earliest possible version is 1.31.

[jingczhang]

Added KEP PR link; changed release targets as adviced.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ffromani]

/remove-lifecycle stale

we're quite active here