From b6c33e695bf50785fc2c425525324037ae137c9b Mon Sep 17 00:00:00 2001 From: blackbird29 Date: Wed, 22 Mar 2017 03:47:47 +0100 Subject: [PATCH] livenessProbe -> periodSeconds (#2832) The field periodSeconds was wrongly referenced as livenessProbe. --- .../configure-liveness-readiness-probes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md index a5c3d8ee56..c17f5abc7b 100644 --- a/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md +++ b/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md @@ -42,7 +42,7 @@ In this exercise, you create a Pod that runs a Container based on the {% include code.html language="yaml" file="exec-liveness.yaml" ghlink="/docs/tasks/configure-pod-container/exec-liveness.yaml" %} In the configuration file, you can see that the Pod has a single Container. -The `livenessProbe` field specifies that the kubelet should perform a liveness +The `periodSeconds` field specifies that the kubelet should perform a liveness probe every 5 seconds. The `initialDelaySeconds` field tells the kubelet that it should wait 5 second before performing the first probe. To perform a probe, the kubelet executes the command `cat /tmp/healthy` in the Container. If the