/sig apps

/area batch

@alculquicondor: The label(s) area/batch cannot be applied, because the repository doesn't have them

@annajung @JamesLaverack James, you mentioned in the sig-apps slack channel that this enhancement is at risk, can you clarify why?

Just to follow up here after further discussion in Slack, that was a mistaken state due to a delay in review. Sorry for the delay on this. I've now marked this enhancement as tracked (and not at risk) for 1.21 on the tracking sheet.

/assign

Hi @alculquicondor,

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 — Code Freeze
• Tuesday, March 16th: Week 10 — Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

Hi @alculquicondor,

A friendly reminder that Code freeze is 3 days away, March 9th EOD PST

Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back.

Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST

Thanks!

Thanks James. There is only one minor bugfix open kubernetes/kubernetes#99865 and I just opened the docs placeholder

Hi @alculquicondor, with the following PRs merged, we will mark this as code complete for the 1.21 release.

• Indexed job implementation kubernetes#98812
• Integration and e2e tests for Indexed job kubernetes#99737
• Fix completed indexed job with repeated indexes kubernetes#99865

Perfect, thank you

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

/remove-lifecycle stale

Probably ready for graduation in 1.24

Hi @alculquicondor ! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd. This enhancements is targeting stable for 1.24
Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo -- Graduate Indexed Job to stable #3113
• KEP status is marked as implementable for this release with latest-milestone: 1.24
• 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.

The status of this enhancement is track as at risk. Please update this issue description to reflect enhancements target
Thanks!

The status for 1.24 Enhancementsis now tracked 🥳

Not sure if this is the right place to ask, but we noticed in the docs following comment:

Note that, although rare, more than one Pod could be started for the same
index, but only one of them will count towards the completion count.

Can it be clarified why that note is needed? And if the pod is started, will it run to completion, or aborted before running or ... ?

Can you open an issue in github.com/kubernetes/website? We can clarify that it will be aborted.

Hi @alculquicondor 👋🏻 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 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!

Hi @alculquicondor 1.24 Enhancements Team here,

With Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, we are currently tracking the following k/k PR:

• Graduate IndexedJob to stable kubernetes#107395

The status of this enhancement is at risk until the PRs are merged. Please let me know if I'm missing any. Thanks!

All good for 1.24 Code Freeze 🥳

Hello @alculquicondor 👋 1.25 Enhancements team here.

Since this feature has been fully implemented and is now GA in K8s version v1.24 🎉 (which is also properly updated in the status of the kep.yaml file).

I'm closing this issue for the purpose of accurate tracking for v1.25. Thank you so much for your valuable contributions. 🙏 🙂

/close

@Priyankasaggu11929: Closing this issue.