Job API managed-by mechanism

[mimowo]

Enhancement Description

• One-line enhancement description: Support managed-by mechanism for Jobs
• Kubernetes Enhancement Proposal: KEP-4368: Support managedBy field for Jobs
• Discussion Link: Job API proposal for MultiKueue, and sig-apps meeting Nov 27,2023, and wg-batch meeting Jan 18 2024
• Primary contact (assignee): @mimowo
• Responsible SIGs: apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.30
  • Beta release target (x.y): 1.32
  • Stable release target (x.y): 1.35
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-4368: Job API managed-by label #4370
    • KEP-4368 update to use managedBy field instead of label #4530
  • Code (k/k) update PR(s):
    • Support for the Job managedBy field (alpha) kubernetes#123273
    • Update Job conformance test for job status updates kubernetes#123751
    • Follow up fix to the job status update test kubernetes#123815
    • Adjust the Job field API comments and validation to the current state kubernetes#123792
    • Fix the comment for the Job managedBy field kubernetes#124793
  • Docs (k/website) update(s):
    • Add docs for Job managedBy field (alpha) website#45132
• Second Alpha (1.31)
  • KEP (k/enhancements) update PR(s):
    • Update the managedBy KEP with fix for terminating pods #4657
  • Code (k/k) update PR(s):
    • Count terminating pods when deleting active pods for failed jobs kubernetes#125175
    • Delay setting terminal Job conditions until all pods are terminal kubernetes#125510
    • Update the count of ready pods when deleting pods kubernetes#125546
  • Docs (k/website) update(s):
    • Update the docs for JobManagedBy and JobPodReplacementPolicy related to pod termination website#46808
• Beta 1.32
  • KEP (k/enhancements) update PR(s):
    • Update "KEP-4368 Job API managed-by mechanism" targeting Beta in 1.32 #4856
  • Code (k/k) update PR(s):
    • Graduate JobManagedBy to Beta in 1.32 kubernetes#127402
    • Fix validation for Job with suspend=true,completions=0 to set Complete condition kubernetes#132614 (1.34)
  • Docs (k/website) update(s):
    • Update docs as JobManagedBy graduates to Beta website#48378
• Stable 1.35
  • KEP (k/enhancements) update PR(s): KEP-4368: Job Managed By; Promote to GA #5583
  • Code (k/k) update PR(s):
    • fix: allow job startTime updates on resume from suspended state kubernetes#134769
    • KEP-4368: Job Managed By; Promote to GA kubernetes#135080
  • Docs (k/website) update(s):
    • [KEP-4368]: Job Managed By; Promote to GA website#52847

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

[mimowo]

/sig apps
/wg batch
/assign

[soltysh]

/label lead-opted-in
/milestone v1.30
/stage beta

[mickeyboxell]

Hello @mimowo 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on [02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024](https://everytimezone.com/s/1ade3dca):.

This enhancement is targeting for stage beta for v1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the [latest template](https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template) has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.30. 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 a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check [here](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval)).

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

• KEP status is marked as implementable for latest-milestone: 1.30.

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