<p>I am having two cluster <code>cluster-1</code> and <code>cluster-2</code>.</p>
<p>In <code>cluster-1</code> deployed <code>service-1</code> in the namespace <code>test-namespace-1</code>. It got deployed successfully and running.</p>
<p>In <code>cluster-2</code> deployed <code>service-1</code> in the namespace <code>test-namespace-1</code>. Deployment status showing error as <code>HTTP probe failed with statuscode: 500</code></p>
<p>When I checked the details, it has two <code>conditions</code></p>
<ol>
<li><code>Processing</code> status as <code>true</code></li>
<li><code>Available</code> status as <code>false</code> and reason is <code>MinimumreplicaUnavailable</code></li>
</ol>
<p>I checked both namespaces quota details.</p>
<ul>
<li>limits.cpu - used:43 hard:90</li>
<li>limits.memory - used:65000Mi hard:96Gi</li>
<li>persistencevolumeclaims - used:8 hard:10</li>
<li>pods - used:35 hard:65</li>
</ul>
<p>other details like request's storage, cpu etc have almost 40% available but in one clsuetr's namespace it is showing success and running and in another cluaster's namespace failed.</p>

Sat
<p>Check your container log and pod's event log.</p>
<p><code>HTTP probe failed with statuscode: 500</code> means your application did not start successfully or returns error in the healthcheck path (liveness/readiness probe) or the initial delay too early for your app to start.</p>
<p>If it's the liveness/readiness probe problem, it is a good idea to also set up the liveness/readiness probe config. See <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/" rel="nofollow noreferrer">official docs</a></p>
<p><code>MinimumreplicaUnavailable</code> means your pod did not scale successfully as intended. If it was scheduling problem (inefficient resources), you should get another error saying &quot;insufficient....&quot; instead.</p>
