From aadb6b466dd8a731c4f30033d51a2afad2cec95f Mon Sep 17 00:00:00 2001
From: Sreeram Venkitesh <40194401+sreeram-venkitesh@users.noreply.github.com>
Date: Tue, 15 Aug 2023 11:45:47 +0530
Subject: [PATCH] Added KEP of the week

---
 _posts/2023-08-13-update.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/_posts/2023-08-13-update.md b/_posts/2023-08-13-update.md
index db61c307..3777ded3 100644
--- a/_posts/2023-08-13-update.md
+++ b/_posts/2023-08-13-update.md
@@ -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