Skip to content

Commit 355bae5

Browse files
authored
Merge pull request #42388 from alculquicondor/finalizers-always
Mark Job tracking with finalizers as always enabled
2 parents 0560375 + 16566d6 commit 355bae5

File tree

2 files changed

+3
-30
lines changed
  • content/en/docs
    • concepts/workloads/controllers
    • reference/labels-annotations-taints

2 files changed

+3
-30
lines changed

content/en/docs/concepts/workloads/controllers/job.md

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -831,32 +831,12 @@ mismatch.
831831

832832
{{< feature-state for_k8s_version="v1.26" state="stable" >}}
833833

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-
840834
The control plane keeps track of the Pods that belong to any Job and notices if
841835
any such Pod is removed from the API server. To do that, the Job controller
842836
creates Pods with the finalizer `batch.kubernetes.io/job-tracking`. The
843837
controller removes the finalizer only after the Pod has been accounted for in
844838
the Job status, allowing the Pod to be removed by other controllers or users.
845839

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-
860840
### Elastic Indexed Jobs
861841

862842
{{< feature-state for_k8s_version="v1.27" state="beta" >}}

content/en/docs/reference/labels-annotations-taints/_index.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1094,17 +1094,10 @@ Example: `batch.kubernetes.io/job-tracking: ""`
10941094

10951095
Used on: Jobs
10961096

1097-
The presence of this annotation on a Job indicates that the control plane is
1097+
The presence of this annotation on a Job used to indicate that the control plane is
10981098
[tracking the Job status using finalizers](/docs/concepts/workloads/controllers/job/#job-tracking-with-finalizers).
1099-
The control plane uses this annotation to safely transition to tracking Jobs
1100-
using finalizers, while the feature is in development.
1101-
You should **not** manually add or remove this annotation.
1102-
1103-
{{< note >}}
1104-
Starting from Kubernetes 1.26, this annotation is deprecated.
1105-
Kubernetes 1.27 and newer will ignore this annotation and always track Jobs
1106-
using finalizers.
1107-
{{< /note >}}
1099+
Adding or removing this annotation no longer has an effect (Kubernetes v1.27 and later)
1100+
All Jobs are tracked with finalizers.
11081101

11091102
### job-name (deprecated) {#job-name}
11101103

0 commit comments

Comments
 (0)