From d5bb436cec796efab670675c48219762e35ec39b Mon Sep 17 00:00:00 2001 From: Chao Xu Date: Wed, 13 May 2015 17:05:12 -0700 Subject: [PATCH] Update k8s201.md to match PR#8011 --- examples/walkthrough/k8s201.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/walkthrough/k8s201.md b/examples/walkthrough/k8s201.md index a8ca8b02acd..17399448d79 100644 --- a/examples/walkthrough/k8s201.md +++ b/examples/walkthrough/k8s201.md @@ -116,7 +116,7 @@ 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 returns "ok" it will be considered a success. + * Container Exec - The Kubelet will execute a command inside your container. If it exits with status 0 it will be considered a success. * 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.