/sig node

/stage alpha
/milestone v1.22

Hi @fromanirh 👋 1.22 Enhancement shadow here.

This enhancement is in good shape, some minor change requests in light of Enhancement Freeze on Thursday May 13th:

• In kep.yaml file, prr-approvers is empty
• Please elaborate and/or link the implementation PR in your Test Plan

Thank you 😊

Hi @fromanirh wave 1.22 Enhancement shadow here.

This enhancement is in good shape, some minor change requests in light of Enhancement Freeze on Thursday May 13th:

• In kep.yaml file, prr-approvers is empty
• Please elaborate and/or link the implementation PR in your Test Plan

Done! thanks for checking!

fixed the issue summary to make it consistent with the KEP

Hi @fromanirh 👋 1.22 Enhancements shadow here.
I just wanted to double check to see if SIG-Node will need to do anything for this enhancement and if so, are they OK with it?
Thanks!

Hi @fromanirh wave 1.22 Enhancements shadow here.
I just wanted to double check to see if SIG-Node will need to do anything for this enhancement and if so, are they OK with it?
Thanks!

Hi @gracenng ! thanks for checking in! I'm waiting for another review indeed. sig-node ack'd this enhancement (https://docs.google.com/document/d/1U10J0WwgWXkdYrqWGGvO8iH2HKeerQAlygnqgDgWv4E/edit#heading=h.y6vnh39j4mih) but unfortunately the sig is a bit overworked. I'll update as soon as possible.

Hi @fromanirh 🌞 1.22 enhancements shadow here.

In light of Code Freeze on July 8th, this enhancement current status is at risk as kubernetes/kubernetes#101432 has not been merged.
Please let me know if there is other code PR associated with this enhancement and feel free to ping me once its merged.

Thanks

Hi @fromanirh, 1.22 enhancements shadow here. Friendly reminder that Code Freeze is tomorrow, July 8th. Feel free to ping me once its merged.

Hi @fromanirh, 1.22 enhancements shadow here. Friendly reminder that Code Freeze is tomorrow, July 8th. Feel free to ping me once its merged.

Hi Grace, thanks for the reminder. I'm working towards the final round of review.

Please note that (of course once the implementation merges) we are planning to go beta not before two releases. So, if the implementation merges in 1.22, we will not promote to beta before 1.24 (was 1.23 before)

@gracenng FYI: kubernetes/kubernetes#101432 (comment)

/label lead-opted-in

Hello @ffromani 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage stable for v1.33 (correct me, if otherwise)
/stage stable

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.33.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would need to update the following:

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

It looks like #5108 will address most of these issues.

• Get KEP-2625: Promote the CPUManager Policy Option full-pcpus-only to GA #5108 merged before the enhancements freeze.

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

Hi @ffromani 👋, 1.33 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

The current status of this enhancement is marked as At risk for enhancement freeze. There are a few requirements mentioned in the comment #2625 (comment) that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

Hello @ffromani 👋, 1.33 Enhancements team here.

Now that PR #5108 has been merged, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

/label tracked/yes

Hello @ffromani 👋, v1.33 Docs Shadow here.

Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?
If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 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!

Hey again @ffromani 👋, 1.33 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025. .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• node: metrics for alignment failures kubernetes#129950
• node: kep-2625: cpu manager policy options GA kubernetes#130535
• I couldn’t find a PR for graduating the feature to Stable. Not sure if it’s completed or not, can you confirm if it’s already done?

Additionally, please let me know if there are any other PRs in k/k not listed above that we should track for this KEP, so that we can maintain accurate status.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as at risk for code freeze.

Hey @ffromani 👋 -- this is Udi (@Udi-Hofesh) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features that fall into (but are not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Hey @ffromani 👋 -- this is Udi (@Udi-Hofesh) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features that fall into (but are not limited to) the following categories:

* This introduces some breaking change(s)

* This has significant impacts and/or implications to users

* ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timelines to keep in mind:

* **02:00 UTC Wednesday, 5th March, 2025**: Feature blog PR freeze

* **Monday, 7th April, 2025**: Feature blogs ready for review

* You can find more in the [release document](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.33#timeline)

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.

thanks for the reminder! I was contemplating adding a feature blog but this feature (non-breaking, nontrivial impact to few users, not particularly long-awaited) is a bit of niche and a bit of limited scope. So I think it would be best to have a cumulative entry later on once we have more cpumanager policy options, and nothing for now (just regular release docs, no highlights yet)

For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

* [node: metrics for alignment failures kubernetes#129950](https://github.com/kubernetes/kubernetes/pull/129950)

* I couldn’t find a PR for graduating the feature to Stable. Not sure if it’s completed or not, can you confirm if it’s already done?

Thanks for checking! I was hoping to merge 129950 quickly, but I was proven wrong. I filed the missing PR, which does not logically depend on 129950, but should be merged only after 129950 is merged: kubernetes/kubernetes#130535

Additionally, please let me know if there are any other PRs in k/k not listed above that we should track for this KEP, so that we can maintain accurate status.

Thanks, I'm also trying my best to track accurately the KEP status. For this work, the linked PRs should be sufficient.

Hey @ffromani 👋 -- this is Udi (@Udi-Hofesh) from the 1.33 Communications Team!
For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!
As you may be aware, feature blogs are a great way to communicate to users about features that fall into (but are not limited to) the following categories:

* This introduces some breaking change(s)

* This has significant impacts and/or implications to users

* ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚
Tip
Some timelines to keep in mind:

* **02:00 UTC Wednesday, 5th March, 2025**: Feature blog PR freeze

* **Monday, 7th April, 2025**: Feature blogs ready for review

* You can find more in the [release document](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.33#timeline)

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.

thanks for the reminder! I was contemplating adding a feature blog but this feature (non-breaking, nontrivial impact to few users, not particularly long-awaited) is a bit of niche and a bit of limited scope. So I think it would be best to have a cumulative entry later on once we have more cpumanager policy options, and nothing for now (just regular release docs, no highlights yet)

@ffromani, as the deadline to submit is only a few hours away, I wanted to double verify that you are opting out (?) You only need to open a placeholder PR at this stage. Lemme know :)

Hey @ffromani 👋 -- this is Udi (@Udi-Hofesh) from the 1.33 Communications Team!
For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!
As you may be aware, feature blogs are a great way to communicate to users about features that fall into (but are not limited to) the following categories:

* This introduces some breaking change(s)

* This has significant impacts and/or implications to users

* ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚
Tip
Some timelines to keep in mind:

* **02:00 UTC Wednesday, 5th March, 2025**: Feature blog PR freeze

* **Monday, 7th April, 2025**: Feature blogs ready for review

* You can find more in the [release document](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.33#timeline)

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.

thanks for the reminder! I was contemplating adding a feature blog but this feature (non-breaking, nontrivial impact to few users, not particularly long-awaited) is a bit of niche and a bit of limited scope. So I think it would be best to have a cumulative entry later on once we have more cpumanager policy options, and nothing for now (just regular release docs, no highlights yet)

@ffromani, as the deadline to submit is only a few hours away, I wanted to double verify that you are opting out (?) You only need to open a placeholder PR at this stage. Lemme know :)

Hi, I double confirm I'm opting out. I really do feel a blog entrey for this option alone is too thin and I'd rather have a single blog entry (perhaps co-authored with other contributors) covering a range of features.
All of these feature blog will require a refresher about modern CPU layout which can take some significant real blog estate, so this seems another reason to group the topics reusing a common introduction.

Hi @ffromani 👋, 1.33 Enhancements team here,

Just a quick friendly reminder as we approach the code freeze later this week, at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

The current status of this enhancement is marked as At risk for code freeze. There are a few requirements mentioned in the comment #2625 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

Hey @ffromani 👋, v1.33 Enhancements team here,

With all the implementation(code related) PRs merged as per the issue description:

• node: metrics for alignment failures kubernetes#129950
• node: kep-2625: cpu manager policy options GA kubernetes#130535

This enhancement is now marked as tracked for code freeze for the v1.33 Code Freeze!

Additionally, please let me know if there are any other PRs in k/k not listed in the description that we should track for this KEP, so that we can maintain accurate status.