whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update beta status for 1.22 probe-level grace periods

Browse Source
This commit is contained in:
Elana Hashman
2021-07-13 15:21:12 -07:00
parent a1fd3a2d57
commit 3f0103cd26
1 changed files with 21 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+21 -6
View File
@@ -429,7 +429,7 @@ to resolve it.
### Probe-level `terminationGracePeriodSeconds` ### Probe-level `terminationGracePeriodSeconds`
{{< feature-state for_k8s_version="v1.21" state="alpha" >}} {{< feature-state for_k8s_version="v1.22" state="beta" >}}
Prior to release 1.21, the pod-level `terminationGracePeriodSeconds` was used Prior to release 1.21, the pod-level `terminationGracePeriodSeconds` was used
for terminating a container that failed its liveness or startup probe. This for terminating a container that failed its liveness or startup probe. This
@@ -437,11 +437,26 @@ coupling was unintended and may have resulted in failed containers taking an
unusually long time to restart when a pod-level `terminationGracePeriodSeconds` unusually long time to restart when a pod-level `terminationGracePeriodSeconds`
was set. was set.
In 1.21, when the feature flag `ProbeTerminationGracePeriod` is enabled, users In 1.21 and beyond, when the feature gate `ProbeTerminationGracePeriod` is
can specify a probe-level `terminationGracePeriodSeconds` as part of the probe enabled, users can specify a probe-level `terminationGracePeriodSeconds` as
specification. When the feature flag is enabled, and both a pod- and part of the probe specification. When the feature gate is enabled, and both a
probe-level `terminationGracePeriodSeconds` are set, the kubelet will use the pod- and probe-level `terminationGracePeriodSeconds` are set, the kubelet will
probe-level value. use the probe-level value.
{{< note >}}
As of Kubernetes 1.22, the `ProbeTerminationGracePeriod` feature gate is only
available on the API Server. The kubelet always honors the probe-level
`terminationGracePeriodSeconds` field if it is present on a Pod.
If you have existing Pods where the `terminationGracePeriodSeconds` field is set and
you no longer wish to use per-probe termination grace periods, you must delete
those existing Pods.
When you (or the control plane, or some other component) create replacement
Pods, and the feature gate `ProbeTerminationGracePeriod` is disabled, then the
API server ignores the Pod-level `terminationGracePeriodSeconds` field, even if
a Pod or pod template specifies it.
{{< /note >}}
For example, For example,