kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #41286 from sairameshv/exec_probe 

Add a caution regarding the `exec` probe mechanism
This commit is contained in:
Kubernetes Prow Robot 2023-06-01 09:29:46 -07:00 committed by GitHub
parent 5f352713b6 0ef0dedf3a
commit 0debd148bf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/concepts/workloads/pods/pod-lifecycle.md
View File

@ -316,6 +316,10 @@ Each probe must define exactly one of these four mechanisms:
the port is open. If the remote system (the container) closes the port is open. If the remote system (the container) closes
the connection immediately after it opens, this counts as healthy. the connection immediately after it opens, this counts as healthy.
{{< caution >}} Unlike the other mechanisms, `exec` probe's implementation involves the creation/forking of multiple processes each time when executed.
As a result, in case of the clusters having higher pod densities, lower intervals of `initialDelaySeconds`, `periodSeconds`, configuring any probe with exec mechanism might introduce an overhead on the cpu usage of the node.
In such scenarios, consider using the alternative probe mechanisms to avoid the overhead.{{< /caution >}}
### Probe outcome ### Probe outcome
Each probe has one of three results: Each probe has one of three results: