<p>i built a little stack in a minikube cluster with :</p>
<ul>
<li>a java spring-boot application into a Pod/Container</li>
<li>a postgres databse into a Pod/Container</li>
</ul>
<p>the spring boot application has to reach spring boot container but it doesn't.
Postgres container seems to start correctly (&quot;&quot;)
but spring boot container does not. At start, i have a message like :</p>
<pre><code>Could not obtain connection to query metadata : HikariPool-1 - Connection is not available, request timed out after 30000ms.
</code></pre>
<p>So i'd like to learn debugging this kind of problem, because i don't know to deal with this error</p>
<p>-is it a network issue ? (pod can't be contacted ?)
-is it a credentials issue ?</p>
<ul>
<li>other ?</li>
</ul>
<p>(pod can't be contacted ?)</p>

it.drive.view
<p>Well, all is ok now. The mistake I made was that I believed I had built the new image, but I kept building it with the same tag. So, the image changed on DockerHub, but the cluster never pulled the new content of the image, because the tagged version had been cached.</p>
<p>When building with a tag N+1, kubernetes then pulled the N+1 version and the pods were started successfully.</p>
<p>My new rule: new docker build --&gt; new tag !!!</p>
