-
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
KEP-4622: Add a TopologyManager policy option for MaxAllowableNUMANodes #4622
Comments
/sig node |
/assign @cyclinder |
I've added this to the tracking sheet for 1.31: |
/label lead-opted-in |
Hello @cyclinder @klueska 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting stage Here's where this enhancement currently stands:
For this KEP, it looks like we still need to do 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! |
In this case we are opting in the new sig-arch recommendations: kubernetes/community@d060ec0 and starting directly to beta stage as the change is very safe and self-contained. |
@ffromani @cyclinder I can update targeting for this enhancement, could you please update the issue description with the stages and targeted milestones accordingly? |
/stage beta |
Hi @Priann, I've updated the PR descriptions, Is this okay with you? and please let me know if you need me to update anything else. |
@cyclinder: The description looks good, please make sure to get #4624 merged before the enhancements freeze deadline! |
@cyclinder @klueska This is super close to being merged it looks like, but we’re at the freeze deadline. Please file an exception if you want this included in the release. |
@prianna We've already received an exception request for this KEP for 1 day. We can keep this as |
Yes, I preemptively filed an exception request yesterday. It looks like the PR is now merged though. |
@klueska Awesome, thanks for the update! I will update the KEP once I get to my laptop. |
Hey @sreeram-venkitesh can you let me know if this one will be officially moved to Tracked for Enhancement Freeze? 👀 |
Yes it will be, I'm traveling right now. I will update it in the board in some time. |
Thanks @sreeram-venkitesh! Sooo hey @cyclinder 👋 from the v1.31 Communications Team! To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use |
KEP is marked as |
Hi @mbianchidev, I'd love to write a feature blog for this, I'll open a Feature Blog placeholder PR these days, thanks! |
Awesome! Let me know if you need anything now or later on :) |
Hi @klueska, Do you think we should write a blog for this kep, if so, I can do that. |
@cyclinder @klueska v1.31 Docs team here. I created a draft PR for this in the release docs. Can you review it? Feel free to add to the PR. |
Hey @cyclinder comms here: have you created a placeholder for the blog? Need any help? Let us know! |
Hi @mbianchidev Thanks for taking care of this. I incorrectly assumed that kubernetes/website#46870 was that placeholder PR, so I didn't create the PR, now let me create it! sorry. |
Hey again @cyclinder 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 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: If you anticipate missing code freeze, you can file an exception request in advance. Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks! |
Thanks for the reminder, I think kubernetes/kubernetes#124148 can be merged before code freeze. |
Hey @cyclinder with the merge of kubernetes/kubernetes#124148 as per the issue, this enhancement is now marked as |
@klueska @ffromani @cyclinder What is our plan for this feature for 1.32? |
I think we can add a metric to record the pod_admission_time at least. |
Enhancement Description
k/enhancements
) update PR(s): KEP-4622: New TopologyManager Policy: max-allowable-numa-nodes #4624k/k
) update PR(s): kubelet: Add a TopologyManager policy option: max-allowable-numa-nodes kubernetes#124148k/website
) update PR(s): KEP-4622: Add docs for TopologyManager policy option for MaxAllowableNUMANodes website#46870k/enhancements
) update PR(s):k/k
) update PR(s): Add a metric to record the pod admission time.Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
Tasks
The text was updated successfully, but these errors were encountered: