@@ -831,32 +831,12 @@ mismatch.
831
831
832
832
{{< feature-state for_k8s_version="v1.26" state="stable" >}}
833
833
834
- {{< note >}}
835
- The control plane doesn't track Jobs using finalizers, if the Jobs were created
836
- when the feature gate ` JobTrackingWithFinalizers ` was disabled, even after you
837
- upgrade the control plane to 1.26.
838
- {{< /note >}}
839
-
840
834
The control plane keeps track of the Pods that belong to any Job and notices if
841
835
any such Pod is removed from the API server. To do that, the Job controller
842
836
creates Pods with the finalizer ` batch.kubernetes.io/job-tracking ` . The
843
837
controller removes the finalizer only after the Pod has been accounted for in
844
838
the Job status, allowing the Pod to be removed by other controllers or users.
845
839
846
- Jobs created before upgrading to Kubernetes 1.26 or before the feature gate
847
- ` JobTrackingWithFinalizers ` is enabled are tracked without the use of Pod
848
- finalizers.
849
- The Job {{< glossary_tooltip term_id="controller" text="controller" >}} updates
850
- the status counters for ` succeeded ` and ` failed ` Pods based only on the Pods
851
- that exist in the cluster. The contol plane can lose track of the progress of
852
- the Job if Pods are deleted from the cluster.
853
-
854
- You can determine if the control plane is tracking a Job using Pod finalizers by
855
- checking if the Job has the annotation
856
- ` batch.kubernetes.io/job-tracking ` . You should ** not** manually add or remove
857
- this annotation from Jobs. Instead, you can recreate the Jobs to ensure they
858
- are tracked using Pod finalizers.
859
-
860
840
### Elastic Indexed Jobs
861
841
862
842
{{< feature-state for_k8s_version="v1.27" state="beta" >}}
0 commit comments