From 7adf359d3afdbf9988828279a34055ed362e7d81 Mon Sep 17 00:00:00 2001 From: Zhiheng Yi Date: Sat, 14 Apr 2018 17:57:58 -0400 Subject: [PATCH] Update pod-lifecycle.md (#8068) * Update pod-lifecycle.md * address feedback * Update pod-lifecycle.md --- docs/concepts/workloads/pods/pod-lifecycle.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/concepts/workloads/pods/pod-lifecycle.md b/docs/concepts/workloads/pods/pod-lifecycle.md index e5dc26e0db..43ca6112a8 100644 --- a/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/docs/concepts/workloads/pods/pod-lifecycle.md @@ -116,6 +116,8 @@ as the liveness probe, but the existence of the readiness probe in the spec mean that the Pod will start without receiving any traffic and only start receiving traffic after the probe starts succeeding. +If your Container needs to work on loading large data, configuration files, or migrations during startup, specify a readiness probe. + If you want your Container to be able to take itself down for maintenance, you can specify a readiness probe that checks an endpoint specific to readiness that is different from the liveness probe. @@ -126,6 +128,8 @@ puts itself into an unready state regardless of whether the readiness probe exis The Pod remains in the unready state while it waits for the Containers in the Pod to stop. +For more information about how to set up a liveness or readiness probe, see [Configure Liveness and Readiness Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/). + ## Pod and Container status For detailed information about Pod Container status, see