<p>Below is the report for liveness &amp; readiness after running <code>kubectl -n mynamespace describe pod pod1</code>:</p>
<pre><code>Liveness:   http-get http://:8080/a/b/c/.well-known/heartbeat delay=3s timeout=3s period=10s #success=1 #failure=3
Readiness:  http-get http://:8080/a/b/c/.well-known/heartbeat delay=3s timeout=3s period=10s #success=1 #failure=3
</code></pre>
<hr />
<ol>
<li><p>Is this the valid(working) url? <code>http://:80/</code></p>
</li>
<li><p>What does <code>#success=1 #failure=3</code> mean?</p>
</li>
</ol>

<p>The results are completely right:</p>
<ul>
<li>http://:8080 indicates that it will try an http-get in port 8080 inside your pod</li>
<li>#success=1 indicates a success threshold of 1 (the default), so the first time it gets an answer it will mark the pod as live or ready</li>
<li>#failure=3 indicates a failure threshold of 3 (the default again), so the third time the call fails will mark it unready or try to restart it.</li>
</ul>
<p>See the official docs: <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes</a></p>
<p>You may try to execute this command to see how the probes are configured:</p>
<pre class="lang-bash prettyprint-override"><code>kubectl -n mynamespace get pod pod1 -o yaml
</code></pre>
