-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-3998: Graduate Job SuccessPolicy to Beta #4702
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
KEP-3998: Graduate Job SuccessPolicy to Beta #4702
Conversation
|
Lastly, make sure to transition this PR from WIP to a final PR 😉 |
| This means that the terminating policies are respected rather than the successPolicies, | ||
| if the Job doesn't have the `FailureTarget` or `SuccessCriteriaMet` conditions yet. | ||
|
|
||
| ### Future Work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we move it out of the scope I would suggest to remove the "Optional Second Alpha" section from Graduation Criteria.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right.
Thank you for reviewing this PR! I definitely finalize this PR soon! |
43687a4 to
2d92c7f
Compare
|
@soltysh @mimowo @alculquicondor @atiratree @wojtek-t I finalized this JobSuccessPolicy graduation KEP. |
mimowo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just minor nits
| In the alpha stage, the upgrade->downgrade->upgrade testing was added in the integration tests | ||
| [here](https://github.com/kubernetes/kubernetes/blob/6346b9d1327c4b8be2398d9715bdae5475e27569/test/integration/job/job_test.go#L794). | ||
|
|
||
| In terms of a manual test for the upgrade and rollback, we can use th v1.30. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| In terms of a manual test for the upgrade and rollback, we can use th v1.30. | |
| In terms of a manual test for the upgrade and rollback, we can use the v1.30. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
|
||
| 3. Simulate upgrade by enabling the feature for api server and control-plane. | ||
|
|
||
| Then, very that the pod with index=2 is terminated and the Job has `SuccessCriteriaMet` and `Complete` conditions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Then, very that the pod with index=2 is terminated and the Job has `SuccessCriteriaMet` and `Complete` conditions. | |
| Then, verify that the pod with index=2 is terminated and the Job has `SuccessCriteriaMet` and `Complete` conditions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
wojtek-t
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just two minor nits from PRR perspective, other than that LGTM
|
|
||
| - E2E tests passed as designed in [TestPlan](#test-plan). | ||
| - Added a new reasons to the existing `job_finished_total` metric in [Monitoring Requirements](#monitoring-requirements). | ||
| - Introduced a new `job_succeeded_total` metric in [Monitoring Requirements](#monitoring-requirements). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any tests for feature enablement/disablement?
nit: You'r mentioning you did an integration test - can you please link it?
[I see it linked below so it's not a blocking issue, but would help for the future]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! Thank you for the suggestion!
| which indicates the following situations: | ||
|
|
||
| - `JobSuccessPolicy` indicates a job is declared as `SuccessCriteriaMet` because the job meets `spec.succesPolicy`. | ||
| - `Completions` indicates a job is declared as `SuccessCriteriaMet` because the job meets `spec.completions`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will enabling / using this feature result in any new API calls?
Please remove the "No" from there :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, I was supposed to remove the "No" in the alpha stage :)
Thank you!
soltysh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are several nits, mostly from Michal, so I'll let him do the final pass.
In general this is good from sig-apps pov
/approve
| - when the job meets the successPolicy and the number of failed pods per indexes exceeds `backoffLimitPerIndex` in all indexes. | ||
|
|
||
| To avoid the above conflicts, terminating policies are evaluated the first before successPolicies. | ||
| This means that the terminating policies are respected rather than the successPolicies, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: the ## Release Signoff Checklist should be updated such that all required bits are checked as needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the section. If I am missing something there, please let me know.
Thanks!
|
/hold |
Signed-off-by: Yuki Iwai <[email protected]>
Signed-off-by: Yuki Iwai <[email protected]>
7242051 to
141ea75
Compare
|
/approve PRR |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: soltysh, tenzen-y, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Thank you! |
|
Thanks all! |
See also: Update the managedBy KEP with fix for terminating pods #4657