Skip to content

Commit 4aa2b6d

Browse files
authored
docs: mention container probes (#29085)
* mention container probe * fix style errors * fix errors
1 parent 2ab22a8 commit 4aa2b6d

File tree

1 file changed

+11
-0
lines changed
  • content/en/docs/concepts/workloads/pods

1 file changed

+11
-0
lines changed

content/en/docs/concepts/workloads/pods/_index.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -282,6 +282,17 @@ on the Kubernetes API server for each static Pod.
282282
This means that the Pods running on a node are visible on the API server,
283283
but cannot be controlled from there.
284284

285+
## Container probes
286+
287+
A _probe_ is a diagnostic performed periodically by the kubelet on a container. To perform a diagnostic, the kubelet can invoke different actions:
288+
289+
- `ExecAction` (performed with the help of the container runtime)
290+
- `TCPSocketAction` (checked directly by the kubelet)
291+
- `HTTPGetAction` (checked directly by the kubelet)
292+
293+
You can read more about [probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes)
294+
in the Pod Lifecycle documentation.
295+
285296
## {{% heading "whatsnext" %}}
286297

287298
* Learn about the [lifecycle of a Pod](/docs/concepts/workloads/pods/pod-lifecycle/).

0 commit comments

Comments
 (0)