/sig scheduling
/sig apps

/milestone v1.23

Hi @ahg-g! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one we would just need the KEP & the PRR file to merge by enhancements freeze :)

Thanks!

Hello @ahg-g! 1.23 Enhancements team here. Just checking in once again, as we approach enhancements freeze on Thursday 09/09.

We just need the KEP & the PRR file to merge by enhancements freeze, to be tracked under the Kubernetes 1.23 release :)

Thanks!

@PriyankaH21 KEP merged including PRR.

Thank you so much, @ahg-g. With the KEP PR merged, this enhancement is ready for the 1.23 enhancements freeze. :)

Hi @ahg-g 👋 1.23 Docs shadow here.

This enhancement is marked as Needs Docs for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 11:59 PM PDT.

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

Thanks!

Hello @ahg-g 👋

Checking in once more as we approach 1.23 code freeze at 6:00 pm PST on Tuesday, November 16.

Please ensure the following items are completed:

• 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 fully merged by the code freeze deadline.
• Have a documentation placeholder PR open by Thursday, November 18.

As always, we are here to help should questions come up.

Thank you so much! 🙂

I opened a docs PR at kubernetes/website#30390

docs PR merged

Thanks so much for the update, @ahg-g

related pr: Make job pod template annotations and labels mutable for suspended jobs that never started

Should we consider schedulerName as well for the next release?

can you state the use case

The queueing system could decide that the job should land in specific Nodes, and these nodes would like their workloads to be scheduled under a specific scheduling profile.

/stage stable
/milestone v1.27
/label lead-opted-in

Hello @ahg-g 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage stable for v1.27 (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.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

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

• Please update the README.md for this enhancement to include the updated test-plan from the KEP template

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

It feels like wasted effort to update the KEP to the new template, the KEP has already been approved by all relevant parties and it includes all relevant information. What do we gain by updating the kep to the new template?

Sent #3799

@marosset KEP updated. PTAL.

It feels like wasted effort to update the KEP to the new template, the KEP has already been approved by all relevant parties and it includes all relevant information. What do we gain by updating the kep to the new template?

Hi @ahg-g - SIG-architecture and others feel that it is important to the long term stability of the project to include discussions on unit and integration during the KEP planning phase.
More discussions are linked in this PR #3279

Thank you for updating the README.md

This enhancement is ready to be traced for graduation to stable in v1.27

/label tracked/yes
/remove-label tracked/no

Hi @ahg-g 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• 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 fully merged by the code freeze deadline.
  • Allow mutating schedulingGates in the Pod template for suspended Jobs kubernetes#115940
  • Graduate JobMutableNodeSchedulingDirectives feature to GA kubernetes#116116

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

Hello @ahg-g ! 👋🏾,

@katmutua 1.27 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

If you already have existing open PRs please link them to the description so we can easily track them. Thanks!

Hi @ahg-g, as @katmutua mentioned, please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This placeholder PR must be created by today, March 16, and should be ready for review on Tuesday, March 21.

@mickeyboxell added, thanks!

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

This is complete

/remove-lifecycle stale