-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indexed Job semantics in Job API #2214
Comments
/sig apps |
/area batch |
@alculquicondor: The label(s) In response to this:
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. |
@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:
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. |
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:
You can:
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
The status of this enhancement is track as |
The status for 1.24 Enhancementsis now |
Not sure if this is the right place to ask, but we noticed in the docs following comment:
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: The status of this enhancement is |
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 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. In response to this:
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. |
Enhancement Description
k/enhancements
) update PR(s): Add KEP for Indexed Job in implementable status #2245k/k
) update PR(s): Indexed job implementation kubernetes#98812k/website
) update PR(s): Documentation for Indexed completion mode website#26958k/enhancements
) update PR(s): Graduate Indexed Job to beta #2616k/k
) update PR(s): Graduate indexed job to beta kubernetes#101292k/website
) update PR(s): Update release status of Indexed Job website#28806 Add details about using the Job completion index website#28980k/enhancements
) update PR(s): Graduate Indexed Job to stable #3113 Add details of scalability test for Indexed Jobs #3239k/k
) update PR(s): Graduate IndexedJob to stable kubernetes#107395k/website
) update PR(s): Graduate Indexed Job to stable website#32395The text was updated successfully, but these errors were encountered: