Mitigate number of status updates

kubernetes · Sep 1, 2021 · aa9e6fe · aa9e6fe
1 parent 2684cc5
commit aa9e6fe
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/keps/sig-apps/2879-ready-pods-job-status/README.md b/keps/sig-apps/2879-ready-pods-job-status/README.md
@@ -94,8 +94,8 @@ field based on the number of Pods that have the `Ready` condition.
 
 ### Risks and Mitigations
 
-An increase in Job status updates. This is capped by the number of times Pods
-reach the ready State, usually once in their lifetime.
+- An increase in Job status updates. To mitigate this, the job controller holds
+  the Pod updates that happen in 100ms before syncing a Job.
 
 ## Design Details
 
@@ -222,8 +222,8 @@ The feature applies to all Jobs, unless the feature gate is disabled.
 
 ###### What are the reasonable SLOs (Service Level Objectives) for the enhancement?
 
-The 99% percentile of Job status updates below 1s, when the controller doesn't
-create new Pods or tracks finishing Pods.
+The 99% percentile of Job status sync (processing+API calls) is below 2s, when
+the controller doesn't create new Pods or tracks finishing Pods.
 
 ###### What are the SLIs (Service Level Indicators) an operator can use to determine the health of the service?
 

diff --git a/keps/sig-apps/2879-ready-pods-job-status/kep.yaml b/keps/sig-apps/2879-ready-pods-job-status/kep.yaml
@@ -20,7 +20,8 @@ stage: alpha
 latest-milestone: "v1.23"
 
 milestone:
-  beta: "v1.23"
+  alpha: "v1.23"
+  beta: "v1.24"
   stable: "v1.25"
 
 feature-gates: