From f69386675de57fcdf6faa5ee2f1ab7de9fec77e9 Mon Sep 17 00:00:00 2001 From: Michal Wozniak Date: Mon, 10 Oct 2022 09:19:15 +0200 Subject: [PATCH] Update of the docs for Beta --- content/en/docs/concepts/workloads/controllers/job.md | 4 ++-- content/en/docs/concepts/workloads/pods/disruptions.md | 5 ++++- .../reference/command-line-tools-reference/feature-gates.md | 2 ++ content/en/docs/tasks/job/pod-failure-policy.md | 6 ------ 4 files changed, 8 insertions(+), 9 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md index a3216c6cf4853..9404d09302c86 100644 --- a/content/en/docs/concepts/workloads/controllers/job.md +++ b/content/en/docs/concepts/workloads/controllers/job.md @@ -697,13 +697,13 @@ mismatch. ### Pod failure policy {#pod-failure-policy} -{{< feature-state for_k8s_version="v1.25" state="alpha" >}} +{{< feature-state for_k8s_version="v1.26" state="beta" >}} {{< note >}} You can only configure a Pod failure policy for a Job if you have the `JobPodFailurePolicy` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled in your cluster. Additionally, it is recommended -to enable the `PodDisruptionsCondition` feature gate in order to be able to detect and handle +to enable the `PodDisruptionConditions` feature gate in order to be able to detect and handle Pod disruption conditions in the Pod failure policy (see also: [Pod disruption conditions](/docs/concepts/workloads/pods/disruptions#pod-disruption-conditions)). Both feature gates are available in Kubernetes v1.25. diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md index 5b1fae8439ae8..62ac384e1bfa4 100644 --- a/content/en/docs/concepts/workloads/pods/disruptions.md +++ b/content/en/docs/concepts/workloads/pods/disruptions.md @@ -232,7 +232,7 @@ can happen, according to: {{< feature-state for_k8s_version="v1.25" state="alpha" >}} {{< note >}} -In order to use this behavior, you must enable the `PodDisruptionsCondition` +In order to use this behavior, you must enable the `PodDisruptionConditions` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in your cluster. {{< /note >}} @@ -254,6 +254,9 @@ indicates one of the following reasons for the Pod termination: `DeletionByPodGC` : Pod, that is bound to a no longer existing Node, is due to be deleted by [Pod garbage collection](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection). +`TerminationByKubelet` +: Pod is being terminated by Kubelet (either due to {{}} or [Graceful Node Shutdown](/docs/concepts/architecture/nodes/#graceful-node-shutdown)) and is due to be deleted by the controller owning the Pod. + {{< note >}} A Pod disruption might be interrupted. The control plane might re-attempt to continue the disruption of the same Pod, but it is not guaranteed. As a result, diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md index 56e13e70a5fb9..6a7e0bd910a3b 100644 --- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md +++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md @@ -396,6 +396,7 @@ different Kubernetes components. | `Initializers` | `false` | Alpha | 1.7 | 1.13 | | `Initializers` | - | Deprecated | 1.14 | - | | `JobPodFailurePolicy` | `false` | Alpha | 1.25 | - | +| `JobPodFailurePolicy` | `true` | Beta | 1.26 | - | | `KubeletConfigFile` | `false` | Alpha | 1.8 | 1.9 | | `KubeletConfigFile` | - | Deprecated | 1.10 | - | | `KubeletPluginsWatcher` | `false` | Alpha | 1.11 | 1.11 | @@ -439,6 +440,7 @@ different Kubernetes components. | `PodDisruptionBudget` | `true` | Beta | 1.5 | 1.20 | | `PodDisruptionBudget` | `true` | GA | 1.21 | - | | `PodDisruptionConditions` | `false` | Alpha | 1.25 | - | +| `PodDisruptionConditions` | `true` | Beta | 1.26 | - | | `PodOverhead` | `false` | Alpha | 1.16 | 1.17 | | `PodOverhead` | `true` | Beta | 1.18 | 1.23 | | `PodOverhead` | `true` | GA | 1.24 | - | diff --git a/content/en/docs/tasks/job/pod-failure-policy.md b/content/en/docs/tasks/job/pod-failure-policy.md index f6243f73ef947..a88890950966d 100644 --- a/content/en/docs/tasks/job/pod-failure-policy.md +++ b/content/en/docs/tasks/job/pod-failure-policy.md @@ -30,12 +30,6 @@ You should already be familiar with the basic use of [Job](/docs/concepts/worklo -{{< note >}} -As the features are in Alpha, prepare the Kubernetes cluster with the two -[feature gates](/docs/reference/command-line-tools-reference/feature-gates/) -enabled: `JobPodFailurePolicy` and `PodDisruptionsCondition`. -{{< /note >}} - ## Using Pod failure policy to avoid unnecessary Pod retries With the following example, you can learn how to use Pod failure policy to