<p>looking to understand the order in which kubenetes examine the pods using the 3 type of probes- startup, readiness and live.</p>
<p>How to understand or design these 3 probes correctly for normal applications? What is the chance of getting conflict or breaking the application if the startup probe has wrong entries</p>

<h2>Startup probe</h2>
<p><strong>This runs first.</strong> When it succeeds, the Readiness Probe and Liveness Probe are run continuously. If this fails, the container is killed.</p>
<p>Use this for &quot;slow staring apps&quot;, you can use the same command as Liveness if you want.</p>
<blockquote>
<p>The kubelet uses startup probes to know when a container application has started. If such a probe is configured, it disables liveness and readiness checks until it succeeds, making sure those probes don't interfere with the application startup. This can be used to adopt liveness checks on slow starting containers, avoiding them getting killed by the kubelet before they are up and running.</p>
</blockquote>
<p>From <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/" rel="nofollow noreferrer">configuring probes</a></p>
<h2>Liveness probe</h2>
<p>This is used to kill the container, in case of a <em>deadlock</em> in the application.</p>
<h2>Readiness probe</h2>
<p>This is used to check that the container can receive traffic.</p>
