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
Elastic Indexed Jobs #3715
Comments
/sig apps |
/wg batch |
/assign |
/stage alpha |
Hello @ahg-g 👋, Enhancements team here. Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage
Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
@Atharva-Shinde can you point to what is missing from the test plan section? Note that the KEP is proposing to graduate to beta right away, so we don't have the integration and e2e tests yet. |
ack. |
@ahg-g, With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
Hi @ahg-g, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. Please feel free to reach out with any questions. Thanks! |
Hey again @ahg-g 👋 Enhancements team here, Here's where this enhancement currently stands:
Also please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Hi @Atharva-Shinde, yes all relevant PRs are merged, I updated the description. |
/stage beta |
@soltysh we will try to graduate this to GA in this release. /label lead-opted-in |
/assign @danielvegamyhre |
/stage stable |
The newly proposed successPolicy changes the meaning of completions. That is we run number of pods according to completions, but we might mark the job as This might not affect Elastic Indexed Jobs feature, but there might be new cross-field validations (completions, successPolicy, indexes). And possible issues might come to light when implementing/testing the new feature with regards to mutable completions field. I think it might be better to wait with graduating this feature to stable until we have a clearer picture. What is your opinion on this? @ahg-g @danielvegamyhre @soltysh |
I am good with that, please feel free to remove it from the milestone. |
That makes sense, thanks for bringing this up. |
That's a good suggestion, thx Filip for catching this. |
@salehsedghpour fyi: this is being removed from 1.30 |
/stage beta |
Hello @ahg-g 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024. Just want to confirm that this work has been postponed. The status of this enhancement is marked as |
/milestone clear |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s): Document elastic indexed Jobs website#39999Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: