<p>Running a Spring Boot application inside a OpenShift Pod. To execute the readiness and liveness probe, I created an appropriate YAML file. However the Pod fails and responds that he was not able to pass the readiness check (after approximately 5 minutes). </p>

<p>My goal is to execute the readiness probe every 20 minutes. But I assume that it is failing because it adds up the initalDelaySeconds together with the periodSeconds. So I guess that the first check after the pod has been started will be executed after 22 minutes.</p>

<p>Following the related configuration of the readiness probe.</p>

<pre><code>readinessProbe:
  failureThreshold: 3
  httpGet:
    path: /actuator/health
    port: 8080
    scheme: HTTP
  initialDelaySeconds: 120
  periodSeconds: 1200
  successThreshold: 1
  timeoutSeconds: 60
</code></pre>

<p>Is my assumption right? How to avoid it (Maybe increase the timeout regarding the kubelet)?</p>

V.Widmer
<p>Your configuration is correct and the <code>initialDelaySeconds</code> and <code>periodSeconds</code> do not sum up. So, the first readinessProbe HTTP call will exactly in 2 min after you start your POD.</p>

<p>I would look for an issue in your app itself, first thing that comes to my mind is that your path is <code>/actuator/health</code>, shouldn't it be just <code>/health</code>? That is the default in case of Spring Boot Actuator.</p>

<p>If that doesn't help, then the best would be to debug it: <code>exec</code> into your container and use <code>curl</code> to check if your health endpoint works correctly (it should return HTTP Code 200).</p>
