enhancements icon indicating copy to clipboard operation
enhancements copied to clipboard
verified publisher icon kubernetes

Reflect PreEnqueue rejections in pod status

Open macsko opened this issue 4 months ago • 13 comments

Enhancement Description

  • One-line enhancement description (can be used as a release note): Updates the pod's status with a clear message when a PreEnqueue plugin rejects it
  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/5501-reflect-preenqueue-rejections-in-pod-status/README.md
  • Discussion Link: https://github.com/kubernetes/kubernetes/issues/130668
  • PRs by stage and milestone:
  • [ ] Beta - v1.35
    • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5510
    • [ ] Code (k/k) update PR(s):
    • [ ] Docs (k/website) update(s): https://github.com/kubernetes/website/pull/52863

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

macsko avatar Aug 26 '25 10:08 macsko

Hi @macsko :wave:, v1.35 Enhancements Lead here.

It looks like this enhancement has been added to the v1.35 milestone, but doesn't yet have the lead-opted-in label. Just a gentle reminder that if you plan to work on this enhancement in v1.35, please have the SIG lead opt-in by adding the lead-opted-in label, which will ensure it gets added to the tracking board.

Thanks!

rayandas avatar Sep 17 '25 17:09 rayandas

Hello @macsko 👋, v1.35 Enhancements team here.

This is a reminder of the upcoming PRR freeze on Thursday 9th October 2025 (AoE) / Friday 10th October 2025, 12:00 UTC.

This enhancement is targeting stage Beta for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • [x] PR open or merged with the KEP's PRR questionnaire filled out.
  • [x] PR open or merged with kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
  • [x] PR open or merged with a PRR approval file with the PRR approver listed for the stage the KEP is targeting.

Note that the PRs are not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC. For more information on the PRR process, see here.

With all the PRR freeze requirements in place, this enhancement is now marked as Tracked for PRR freeze! Please keep the issue description up-to-date with appropriate stages as well.

/label tracked/yes

rayandas avatar Oct 03 '25 18:10 rayandas

Hello @macsko 👋, v1.35 Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC.

This enhancement is targeting stage Beta for v1.35 (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.35.
  • [ ] 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).

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

  • Merging the PR https://github.com/kubernetes/enhancements/pull/5510 will check all the requirements and mark this KEP as tracked.

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!

rayandas avatar Oct 13 '25 19:10 rayandas

As the PR https://github.com/kubernetes/enhancements/pull/5510 is now merged, marking this KEP as Tracked for Enhancements freeze.

rayandas avatar Oct 15 '25 15:10 rayandas

Hello @macsko :wave:, v1.35 Docs Shadow here.

Does this enhancement work planned for v1.35 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.35 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 23th October 2025.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

kernel-kun avatar Oct 16 '25 06:10 kernel-kun

Hi @macsko 👋, this is Swathi (@SwathiR03 ) from the 1.35 Communications Team!

For the 1.35 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 which 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, where the blog would go a long way to cover the journey in more 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 Friday, the 31st of October? For more information about writing a blog, please find the blog contribution guidelines 📚

[!Tip] Some timelines to keep in mind:

  • 12:00 UTC Friday, 31st October: Feature blog PR freeze
  • Friday, 21st November: Feature blogs ready for review
  • You can find more in the release document

[!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.

SwathiR03 avatar Oct 18 '25 09:10 SwathiR03

Hello @macsko 👋, this is Tushar Mittal (@kernel-kun) from v1.35 Release Docs team! We are closing in on the Placeholder PR deadline, Thursday 23rd October 2025. I'm dropping a reminder to please follow the guidelines mentioned in the quoted comment (https://github.com/kubernetes/enhancements/issues/5501#issuecomment-3409434691)

Hello @macsko 👋, v1.35 Docs Shadow here.

Does this enhancement work planned for v1.35 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.35 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 23th October 2025.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

kernel-kun avatar Oct 21 '25 13:10 kernel-kun

Hi, created https://github.com/kubernetes/website/pull/52863

macsko avatar Oct 22 '25 08:10 macsko

Hi @macsko 👋, Swathi(@SwathiR03) from the 1.35 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 12:00 UTC, Friday, the 31st of October. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

[!Tip] Some timelines to keep in mind:

  • 12:00 UTC Friday, 31st October: Feature blog PR freeze
  • Friday, 21st November: Feature blogs ready for review
  • You can find more in the release document

[!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.

SwathiR03 avatar Oct 26 '25 05:10 SwathiR03

Hey again @macsko 👋, v1.35 Enhancements team here,

Just checking in as we approach code freeze and test freeze on Thursday 6th November 2025 (AoE) / Friday 7th November 2025, 12:00 UTC.

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.

Please let me know (and keep the issue description updated) if there are any open PRs in k/k that we should track for this KEP, so that we can maintain accurate status.

If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of k/k), please link the relevant PRs in the issue description for visibility. Alternatively, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.

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.

rayandas avatar Nov 01 '25 16:11 rayandas

HI @rayandas, work on this feature has been postponed to v1.36.

macsko avatar Nov 03 '25 07:11 macsko

@macsko thanks for the update. Marking this KEP as Deferred.

rayandas avatar Nov 06 '25 15:11 rayandas

Hi @macsko 👋 v1.35 Enhancements Team here.

We are nearing the close of the v1.35 release. As part of the end of release cleanup, we are removing the lead-opted-in label to prepare for the next cycle.

If you would like this enhancement to be considered for the next release, please have the SIG lead opt in again by re adding the label and setting the appropriate milestone for the new release. This ensures the enhancement appears on the tracking board.

Thanks!

/remove-label lead-opted-in

rayandas avatar Dec 15 '25 16:12 rayandas