From 042e57a1778c3d54a18ff8910782f3dc1bc811a6 Mon Sep 17 00:00:00 2001 From: Chris O'Haver Date: Thu, 1 Oct 2020 11:03:34 -0400 Subject: [PATCH] fix lameduck docs (#4169) Signed-off-by: Chris O'Haver --- plugin/health/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plugin/health/README.md b/plugin/health/README.md index 2142a7e0b..1247cb088 100644 --- a/plugin/health/README.md +++ b/plugin/health/README.md @@ -26,8 +26,8 @@ health [ADDRESS] { } ~~~ -* Where `lameduck` will make the process unhealthy then *wait* for **DURATION** before the process - shuts down. +* Where `lameduck` will delay shutdown for **DURATION**. /health will still answer 200 OK. + Note: The *ready* plugin will not answer OK while CoreDNS is in lameduck mode prior to shutdown. If you have multiple Server Blocks, *health* can only be enabled in one of them (as it is process wide). If you really need multiple endpoints, you must run health endpoints on different ports: