Track Ready Pods in Job status

[alculquicondor]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add a ready field to the Job status that track the number of Pods with the Ready condition.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2879-ready-pods-job-status
• Discussion Link: Add running field to Job status kubernetes#104422
• Primary contact (assignee): @alculquicondor
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.24
  • Stable release target (x.y): 1.29
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-2879: Add count of ready Pods in Job status #2880
  • Code (k/k) update PR(s): Track ready pods in Job status kubernetes#104915
  • Docs (k/website) update PR(s): Add JobReadyPods feature gate website#30593
• Beta
  • KEP (k/enhancements) update PR(s): Graduate Ready Pods in Job status to Beta #3111, Add load test results for JobReadyPods #3249
  • Code (k/k) update PR(s): Graduate JobReadyPods to beta kubernetes#107476
  • Docs (k/website) update PR(s): Graduate JobReadyPods to beta website#32396
• Stable
  • KEP (k/enhancements) update PR(s): Graduate KEP-2879 PodsReady to stable #4237
  • Code (k/k) update PR(s):
    • e2e: add test for checking ready of job status  kubernetes#121300
    • Graduate JobReadyPods to stable kubernetes#121302
  • Docs (k/website) update PR(s): Docs update for JobPodsReady in GA website#43387

[alculquicondor]

/assign
/sig apps

[salaxander]

/milestone v1.23

[salaxander]

Hi @alculquicondor! 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.
• [X ] KEP status is marked as implementable
• [X ] KEP has a test plan section filled out.
• [X ] KEP has up to date graduation criteria.
• [ X] 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 to merge by enhancements freeze :)

Thanks!

[jlbutler]

Hi @alculquicondor 👋 1.23 Docs lead 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!

[chrisnegus]

Hi @alculquicondor 👋 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!

[reylejano]

Hi @alculquicondor and @kubernetes/sig-apps-misc ,
1.23 Release Lead here. We're a day past the 1.23 Docs Placeholder PR deadline and this enhancement is marked as 'Needs Docs' for 1.23 and is without a linked Doc PR to the dev-1.23 branch in k/website.

Since this feature is going to be alpha in 1.23, is this enhancement feature-gated? Does the Feature Gates page need to be updated with this enhancement? Does other documentation on kubernetes.io need to be updated or created? If so, please create a PR to the dev-1.23 branch in k/website ASAP

[alculquicondor]

The PR is up. Sorry about the delay. I missed this before going on vacation.

[chrisnegus]

The PR is up. Sorry about the delay. I missed this before going on vacation.

Not a problem. Thanks so much for getting this done! Is the feature gate information all that needs to be updated or are more docs needed? If that's it, I'll work on getting it looked at and merged.

[alculquicondor]

that's all that's needed. The rest is already part of the API reference.

[soltysh]

/milestone v1.24

[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

We can graduate to GA in 1.28

[kannon92]

/remove-lifecycle stale

We can graduate to GA in 1.28

What items is needed for this?

[alculquicondor]

https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2879-ready-pods-job-status#ga

Given that there were no bug reports, the only item left is exploring different batch sizes to see if we get better scale without sacrificing latency.

[kannon92]

Ah, I may need someone else to do that. I don't really have a good k8 environment for doing performance testing.

[soltysh]

/milestone v1.29
/label lead-opted-in

[jeremyrickard]

@soltysh should we change the stage on this to stable?

[soltysh]

@soltysh should we change the stage on this to stable?

Good catch, thx

/stage stable

[salehsedghpour]

Hello @alculquicondor 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Friday, 6th October 2023.

This enhancement is targeting for stage stable for 1.29 (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 implemented for latest-milestone: 1.29.
• 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 add/update the following:

• The status in kep.yaml should be marked as implemented.

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!

[alculquicondor]

Oops, opened a PR to fix the KEP.

/assign @mimowo
who is assisting with the graduation.

[alculquicondor]

@salehsedghpour the KEP update PR is merged

[salehsedghpour]

@alculquicondor thanks for the update. With this, this enhancement is now tracked for the enhancement freeze.

[katcosgrove]

Hey there @alculquicondor and @mimowo 👋, v1.29 Docs Lead here.
Does this enhancement work planned for v1.29 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[salehsedghpour]

Hey again @alculquicondor 👋 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November.

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 PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

With all this, the status of this KEP is tracked for code freeze.

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

[James-Quigley]

Hi @alculquicondor 👋 from the v1.29 Communications Release Team! We would like to check if you have any plans to publish blogs for this KEP regarding new features, removals, and deprecations for this release.
If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)
Here's the 1.29 Calendar

[alculquicondor]

No plans, thanks :)