Job tracking without lingering Pods

[alculquicondor]

Enhancement Description

• One-line enhancement description (can be used as a release note): Job controller keeps track of Pod completions in status without relaying on lingering Pods.

• Kubernetes Enhancement Proposal: https://git.k8s.io/enhancements/keps/sig-apps/2307-job-tracking-without-lingering-pods

• Discussion Link: Job controller should not rely on calculating pod for its status kubernetes#28486

• Primary contact (assignee): alculquicondor

• Responsible SIGs: apps

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.22
  • Beta release target (x.y): 1.23
  • Stable release target (x.y): 1.26

• Alpha

  • KEP (k/enhancements) update PR(s): Add KEP for job tracking in implementable status #2308 Update KEP for Job Tracking #2585
  • Code (k/k) update PR(s): Track Job completion through Pod finalizers and status kubernetes#98238
  • Docs (k/website) update PR(s): Add feature gate JobTrackingWithFinalizers website#28841

• Beta

  • KEP (k/enhancements) update PR(s): Graduate JobTrackingWithFinalizers to beta in 1.23 #2874
  • Code (k/k) update PR(s): Roll-forward: Beta requirements for JobTrackingWithFinalizers  kubernetes#105197 Graduate JobTrackingWithFinalizers to beta kubernetes#105687
  • Docs (k/website) update(s): Graduate JobTrackingWithFinalizers to beta website#30423

• Stable

  • KEP (k/enhancements) update PR(s): KEP-2307: Graduate JobTrackingWithFinalizers to GA #3482
  • Code (k/k) update PR(s):
    • Add metric for terminated pods with tracking finalizer kubernetes#113176
    • Add benchmark for large indexed job kubernetes#113478
    • Graduate JobTrackingWithFinalizers to stable kubernetes#113510
  • Docs (k/website) update(s):
    • Graduate JobTrackingWithFinalizers to stable website#37764
    • Add blog post for job tracking with finalizers GA website#37438

/sig apps

[alculquicondor]

/sig apps

[alculquicondor]

/assign

[alculquicondor]

It looks like #2232 is almost there. Once it merges, we would have very little time to handle conflicts and go through reviews. So we would likely be deferring this enhancement to 1.22.

cc @ahg-g @soltysh

[ahg-g]

/milestone v1.22

[ahg-g]

@alculquicondor can you update the links to the merged KEP and the open implementation PRs please

[gracenng]

Hi @alculquicondor 👋 1.22 Enhancement shadow here.

This enhancement is in good shape, some minor change requests in light of Enhancement Freeze on Thursday May 13th:

• In KEP.yaml, latest-milestone has not been updated
• In KEP.yaml, milestone (alpha: v1.21, beta: v1.22) doesn't match your current stage

Thanks!

[alculquicondor]

Hi @gracenng, it is up to date https://github.com/kubernetes/enhancements/blob/master/keps/sig-apps/2307-job-tracking-without-lingering-pods/kep.yaml
Perhaps you missed the last PR?

[gracenng]

My apologies @alculquicondor, I did miss that PR. I've updated Enhancement track sheet and this issue is no longer at risk.

[gracenng]

Hi @alculquicondor 👋 1.22 Enhancements shadow here.
I just wanted to check to see if SIG-Apps will need to do anything for this enhancement and if so, are they OK with it?
Thanks!

[soltysh]

Yup, sig-apps is aware and tracking this development.

[chrisnegus]

Hi @alculquicondor ! I'm @chrisnegus , a Docs Shadow for release 1.22.
This enhancement is marked as Needs Docs for the 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the kubernetes/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.

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

Thank you!

[gracenng]

Hi @alculquicondor 🌞 1.22 enhancements shadow here.

In light of Code Freeze on July 8th, this enhancement current status is at risk as k/k#98238 has not been merged.

Please let me know if there is other code PR associated with this enhancement and feel free to ping me once its merged.

Thanks

[alculquicondor]

Thanks Grace. The PR is approved by the SIG, but still awaiting for api-review. There are no more PRs.

[gracenng]

Hi @alculquicondor 🌷 1.22 enhancements shadow here.

A friendly reminder that Code Freeze is tomorrow, on July 8th. Please also be mindful of the docs PR deadline on July 9th

Thanks

[marosset]

Hi @alculquicondor 👋,

It looks like all of the code PRs for this enhancement have been merged so this enhancement is once again tracked for the v1.26 release.

Thanks!

[marosset]

Hi @alculquicondor - since this enhancement has graduated to stable can you please update https://github.com/kubernetes/enhancements/blob/master/keps/sig-apps/2307-job-tracking-without-lingering-pods/kep.yaml setting the status to implemented and then close this issue.
Thanks!

[alculquicondor]

We still have a few deprecations and removals to do in the next versions, as mentioned in the KEP. Is that fine?

cross reference: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2307-job-tracking-without-lingering-pods#deprecation

[marosset]

My mistake! Please keep this issue open until the deprecations / removals are complete.

/milestone clear

[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

[alculquicondor]

/remove-lifecycle stale

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[alculquicondor]

/remove-lifecycle stale

All the post GA requirements are completed.

/close

[k8s-ci-robot]

@alculquicondor: Closing this issue.

In response to this:

/remove-lifecycle stale

All the post GA requirements are completed.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.