github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-08 20:50:24 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #11352 from JanetKuo/docs-reachable

Browse Source 
Ensure all docs and examples in user guide are reachable
This commit is contained in:
Brian Grant
2015-07-16 23:33:45 -07:00
parent 1ee86d05cb b0c68c4b81
commit 5f34630aca
29 changed files with 75 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user-guide/walkthrough/k8s201.md
View File

@@ -249,8 +249,8 @@ Kubelet to ensure that your application is operating correctly for a definition
Currently, there are three types of application health checks that you can choose from:
* HTTP Health Checks - The Kubelet will call a web hook. If it returns between 200 and 399, it is considered success, failure otherwise.
* Container Exec - The Kubelet will execute a command inside your container. If it exits with status 0 it will be considered a success.
* HTTP Health Checks - The Kubelet will call a web hook. If it returns between 200 and 399, it is considered success, failure otherwise. See health check examples [here](../liveness/).
* Container Exec - The Kubelet will execute a command inside your container. If it exits with status 0 it will be considered a success. See health check examples [here](../liveness/).
* TCP Socket - The Kubelet will attempt to open a socket to your container. If it can establish a connection, the container is considered healthy, if it can't it is considered a failure.
In all cases, if the Kubelet discovers a failure, the container is restarted.