Skip to content
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

Added KEP of the week for 8/13 issue #217

Merged
merged 1 commit into from
Aug 15, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions _posts/2023-08-13-update.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,12 @@ Patch releases have been [delayed until August 23rd](https://groups.google.com/a

## KEP of the Week

[KEP 3850 - Backoff Limits Per Index For Indexed Jobs](https://features.k8s.io/3850)

This KEP extends the Jobs API to support indexes for jobs, where the backoff limit is per index. The job can continue executing even if some of its indexes are failing. Currently, the indexes of an indexed job share a common backoff limit. When the job reaches this common backoff limit, the job is marked as failed by the job controller even if there are indexes which are yet to run to completion. The current implementation is not efficient if the indexes are truly independent of each other. If one index fails, the entire job would be marked as failed.

The proposed solution involves adding a new policy where the backoff limit controls the number of retries per index of the job. All indexes of the job execute until they succeed or fail. A new API field to control the number of failed indexes is also proposed. This KEP was authored by [Michał Woźniak](https://github.com/mimowo) and [jensentanlo](https://github.com/jensentanlo) and is in alpha in v1.28


## Other Merges

Expand Down