<p>I'm configuring startup/liveness/readiness probes for kubernetes deployments serving spring boot services. As of the spring boot documentation it's best practice to use the corresponding liveness &amp; readiness actuator endpoints as describes here:
<a href="https://spring.io/blog/2020/03/25/liveness-and-readiness-probes-with-spring-boot" rel="nofollow noreferrer">https://spring.io/blog/2020/03/25/liveness-and-readiness-probes-with-spring-boot</a></p>
<p>What do you use for your startup probe?
What are your recommendations for failureThreshold, delay, period and timeout values?
Did you encounter issues when deploying isito sidecars to an existing setup?</p>

dkmob
<p>I use the paths <code>/actuator/health/readiness</code> and <code>/actuator/health/liveness</code> :</p>
<pre><code>readinessProbe:
  initialDelaySeconds: 120
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 5
  failureThreshold: 3
  httpGet:
    scheme: HTTP
    path: /actuator/health/readiness
    port: 8080

livenessProbe:
  initialDelaySeconds: 120
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 5
  failureThreshold: 3
  httpGet:
    scheme: HTTP
    path: /actuator/health/liveness
    port: 8080
</code></pre>
<p>for the recommendations, it depends on your needs and policies actually ( <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/</a> )</p>
<p>no istio sidecars issues with this :)</p>
<p>do not forget to activate the endpoints in properties (cf <a href="https://www.baeldung.com/spring-liveness-readiness-probes" rel="nofollow noreferrer">https://www.baeldung.com/spring-liveness-readiness-probes</a>):</p>
<pre><code>management.endpoint.health.probes.enabled=true
management.health.livenessState.enabled=true
management.health.readinessState.enabled=true
</code></pre>
