Mutable scheduling directives for suspended Jobs

[ahg-g]

Enhancement Description

• One-line enhancement description (can be used as a release note): make node affinity mutable for jobs
• Kubernetes Enhancement Proposal:
• Discussion Link: Make scheduling directives mutable for Jobs kubernetes#104714
• Primary contact (assignee): @ahg-g
• Responsible SIGs: scheduling
• Enhancement target (which target equals to which milestone):
  • Beta release target (x.y): 1.23
  • Stable release target (x.y): 1.27
• Beta
  • KEP (k/enhancements) update PR(s): KEP-2926: Allow updating scheduling directives of suspended jobs #2931
  • Code (k/k) update PR(s): Allow updating scheduling directives of suspended jobs that never started kubernetes#105479
  • Docs (k/website) update PR(s): Add docs for JobMutableNodeSchedulingDirectives website#30390
• Stable
  • KEP (k/enhancements) update PR(s):
    KEP-2926: Graduate mutable scheduling directives to stable #3709
  • Code (k/k) update PR(s):
    • Graduate JobMutableNodeSchedulingDirectives feature to GA kubernetes#116116
    • Allow mutating schedulingGates in the Pod template for suspended Jobs kubernetes#115940
  • Docs (k/website) update(s): Graduate JobMutableNodeSchedulingDirectives to GA website#40063

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

[ahg-g]

/sig scheduling
/sig apps

[salaxander]

/milestone v1.23

[Priyankasaggu11929]

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!

[Priyankasaggu11929]

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!

[ahg-g]

@PriyankaH21 KEP merged including PRR.

[Priyankasaggu11929]

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

[nate-double-u]

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!

[Priyankasaggu11929]

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! 🙂

[ahg-g]

I opened a docs PR at kubernetes/website#30390

[ahg-g]

docs PR merged

[Priyankasaggu11929]

Thanks so much for the update, @ahg-g

[kerthcet]

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

[alculquicondor]

Should we consider schedulerName as well for the next release?

[ahg-g]

can you state the use case

[alculquicondor]

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.

[marosset]

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

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

[marosset]

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!

[katmutua]

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!

[mickeyboxell]

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.

[ahg-g]

@mickeyboxell added, thanks!

[k8s-triage-robot]

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

[ahg-g]

This is complete

[alculquicondor]

/remove-lifecycle stale