-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing #4540
Comments
… to system daemons and interrupt processing KEP issue link: kubernetes#4540 Signed-off-by: Jing Zhang <jing.c.zhang.ext@nokia.com>
Hi, thanks for filing the issue. Unfortunately the 1.30 release is already in code freeze, so the earliest possible version is 1.31. |
Added KEP PR link; changed release targets as adviced. |
… to system daemons and interrupt processing KEP issue link: kubernetes#4540 Signed-off-by: Jing Zhang <jing.c.zhang.ext@nokia.com>
… to system daemons and interrupt processing KEP issue link: kubernetes#4540 Signed-off-by: Jing Zhang <jing.c.zhang.ext@nokia.com>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale we're quite active here |
… to system daemons and interrupt processing KEP issue link: kubernetes#4540 Signed-off-by: Jing Zhang <jing.c.zhang.ext@nokia.com>
… to system daemons and interrupt processing KEP issue link: kubernetes#4540 Signed-off-by: Jing Zhang <jing.c.zhang.ext@nokia.com>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/milestone v1.32 |
Hello @jingczhang 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024. This enhancement is targeting stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
@jingczhang need to opt in the Production Readiness Review (PRR) flow, the deadline is tomorrow Oct 3, 2024. Just opting in is required, the actual review will happen later.
I think you can start adding @soltysh as approver, the PRR team will suggest rebalancing with different approver as they see fit. EDIT: another example: https://github.com/kubernetes/enhancements/blob/2626c678b2c62b6814c0a73ce4c0e276dcdbed1e/keps/prod-readiness/sig-windows/4885.yaml (note the above example is sig-windows, you will need to use sig-node) |
KEP-4540: Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing #4540
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hi @jingczhang 👋, 1.32 Release Docs Lead here. Does this enhancement work planned for 1.32 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hello @jingczhang , 👋🏼 this is Edith from the v1.32 Communications Team! 🙂 We’d love for you to consider writing a feature blog about your enhancement! ✍ To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024 🗓 . For more information about writing a blog, see the blog contribution guidelines. Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release. |
let's please add kubernetes/kubernetes#127506 among the code changes we need for alpha |
Hi @chanieljdan, thank you for the detailed instructions, I will create doc PR to add this new 'strict-cpu-reservation" option to the existing Kubelet CPU Manager static policy options https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#static-policy-options. |
Hi @edithturn, thank you for detailed instructions, yes, we do plan to write a bug for this feature. I will create a feature blog PR per your instruction. |
Hi @chanieljdan, please find the documentation PR for this feature: |
Hi @edithturn, please find the blog PR for this feature: |
Hey again @jingczhang 👋 v1.32 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 . Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP): Additionally, please let me know if there are any other PRs in k/k not listed in the description or not linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status. The status of this enhancement is marked as at risk for code freeze. If you anticipate missing code freeze, you can file an exception request in advance. Thank you! |
@jingczhang could you please add kubernetes/kubernetes#127506 to the list of the code changes required to this KEP? |
Done. I hope you get this one in asap. Thank you. |
With all PRs merged, this enhancement is now |
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
k/enhancements
) update PR(s): KEP-4540: Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing #4540 #4541k/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#127506k/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#48371Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: