Difference between revisions of "TerminationGracePeriodSeconds"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{lc}} | ||
[[Kubernetes v1.28]] (Aug 2023) | [[Kubernetes v1.28]] (Aug 2023) | ||
| Line 4: | Line 5: | ||
pod- and probe-level | pod- and probe-level | ||
| + | |||
| + | |||
| + | terminationGracePeriodSeconds: configure a grace period for the kubelet to wait between triggering a shut down of the failed container, and then forcing the container runtime to stop that container. The default is to inherit the Pod-level value for terminationGracePeriodSeconds (30 seconds if not specified), and the minimum value is 1. See probe-level terminationGracePeriodSeconds for more detail. | ||
== Related == | == Related == | ||
Latest revision as of 14:08, 5 November 2024
Kubernetes v1.28 (Aug 2023)
pod- and probe-level
terminationGracePeriodSeconds: configure a grace period for the kubelet to wait between triggering a shut down of the failed container, and then forcing the container runtime to stop that container. The default is to inherit the Pod-level value for terminationGracePeriodSeconds (30 seconds if not specified), and the minimum value is 1. See probe-level terminationGracePeriodSeconds for more detail.
Related[edit]
- Container Lifecycle Hooks
- HTTP probes
- TCP probes
- Probe-level
- geth:
Unclean shutdown detected - Successfully pulled image
See also[edit]
Advertising:
