<p>I have implemented spring actuator health endpoints and added this in the Livelines probe - 
http-get <a href="http://:8080/actuator/health" rel="nofollow noreferrer">http://:8080/actuator/health</a></p>

<p>when i describe the pod I don't see the #success counter is increasing</p>

<p>http-get <a href="http://:8080/actuator/health" rel="nofollow noreferrer">http://:8080/actuator/health</a> delay=60s timeout=20s period=10s #success=1 #failure=3</p>

<p>How to know if the liveliness probe is actually running with the default actuator's health endpoint</p>

dvlpr
<p>The value of success here is <strong>successThreshold</strong>.  It is <strong>not a counter field</strong> </p>

<p><code>kubectl explain pod.spec.containers.livenessProbe.successThreshold</code></p>

<pre><code>DESCRIPTION:
     Minimum consecutive successes for the probe to be considered successful
     after having failed. Defaults to 1. Must be 1 for liveness. Minimum value
     is 1.

</code></pre>

<p>similarly there is a failure threshold</p>

<p><code>kubectl explain pod.spec.containers.livenessProbe.failureThreshold
</code></p>

<blockquote>
  <p>When a Pod starts and the probe fails, Kubernetes will try failureThreshold times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready. Defaults to 3. Minimum value is 1.<a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes" rel="nofollow noreferrer">configure-probes</a></p>
</blockquote>

<hr>

<blockquote>
  <p>How to know if the liveliness probe is actually running with the default actuator's health endpoint</p>
</blockquote>

<p>check the logs of your pod </p>

<p><code>kubectl logs -f $pod</code></p>

<p>or check the log of kubelet, which is probing the pod </p>

<p><code>journalctl -f -u kubelet</code></p>
