Pod Generation

[natasha41575]

Enhancement Description

• One-line enhancement description (can be used as a release note): Start using Generation and ObservedGeneration in pods
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/5067-pod-generation
• Discussion Link: https://docs.google.com/document/d/10m0vdWbjqF_q_f1_N3gVOD5YeNn09BwFcVVycG_MoEY/edit?usp=sharing
• Primary contact (assignee): @natasha41575
• Responsible SIGs: SIG Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y): 1.34
  • Stable release target (x.y): 1.35
• Alpha
  • KEP (k/enhancements) update PR(s): KEP 5067: Pod Generation KEP creation #5068
  • Code (k/k) update PR(s):
    • start setting pod metadata.generation kubernetes#130181
  • Docs (k/website) update PR(s):

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

[natasha41575]

/sig node

[natasha41575]

fyi @tallclair

[tallclair]

/assign @natasha41575

[tallclair]

/milestone v1.33

[haircommander]

/label lead-opted-in

[bianbbc87]

Hello @natasha41575 👋, 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 alpha for v1.33 (correct me, if otherwise)

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. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

With all the KEP requirements 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 enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[dipesh-rawat]

Hi @natasha41575 👋, 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 #5067 (comment) that still need to be completed.

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

[natasha41575]

@bianbbc87 @dipesh-rawat The KEP PR #5068 is now merged, which fulfils the requirements in #5067 (comment) so I believe we should be good to go for the v1.33 enhancements freeze.

[dipesh-rawat]

@natasha41575 Now that PR #5068 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!
(cc: @bianbbc87)

/label tracked/yes

[rayandas]

Hello @natasha41575 👋, v1.33 Docs Lead 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!