<p>The below snippet is taken from default Corefile of coredns.</p>
<pre><code>data:  
  Corefile: |    
  .:53 {
        errors
        health {
            lameduck 5s
        }
        ready
</code></pre>
<p>In this snippet, health plugin is used to report health status to http://localhost:8080/health. If 200 OK is reported means healthy coredns pod. But I have few queries,
If anything other than 200 OK is reported as health status of coredns pod, will kubernetes destroy and recreate the coredns pod ?  Or how it will be handled by kubernetes?</p>
<p>If coredns pod is unhealthy, how is it handled to make it healthy? will kubernetes automatically take care of ensuring a healthy coredns pod ? What is the advised lameduck duration? Based on what parameters, we can come to a appropriate lameduck duration.</p>
<p>It would be really helpful if anyone can comment on this. Thanks in advance!</p>

anonymous user
<p>I have coredns deployed on a cluster in the kube-system namespace:</p>
<p><em>kubectl describe deploy coredns -n kube-system</em></p>
<p>Output:
Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=10s #success=1 #failure=3</p>
<p>The Liveness/Readiness probes that are used for this must be configured</p>
