<p>When using helm install/upgrade in some percentage of the time I get this failure:</p>
<pre><code>Failed to install app MyApp. Error: UPGRADE FAILED: timed out waiting for the condition
</code></pre>
<p>This is because the app sometimes needs a bit more time to be up and running.</p>
<p>When I get this message helm doesn't stop the install/upgrade, but still works on it, which will be succeed by the end. And my whole cluster will be fully functional. <br>
However helm still shows this failed status for the release.<br> On one hand it is pretty annoying, on the other hand it can mess up a correctly installed release.</p>
<p>How to remove this false error and get into a 'deployed' state(without a new install/upgrade)?</p>

<p>What you might find useful here are the two following options:</p>
<blockquote>
<ul>
<li><p><code>--wait</code>: Waits until all Pods are in a ready state, PVCs are bound, Deployments have minimum (<code>Desired</code> minus <code>maxUnavailable</code>) Pods in
ready state and Services have an IP address (and Ingress if a
LoadBalancer) before marking the release as successful. It will wait
for as long as the <code>--timeout</code> value. If timeout is reached, the
release will be marked as <code>FAILED</code>. Note: In scenarios where
Deployment has replicas set to 1 and <code>maxUnavailable</code> is not set to 0
as part of rolling update strategy, <code>--wait</code> will return as ready as
it has satisfied the minimum Pod in ready condition.</p>
</li>
<li><p><code>--timeout</code>: A value in seconds to wait for Kubernetes commands to complete This defaults to 5m0s</p>
</li>
</ul>
</blockquote>
<p>Helm install and upgrade commands include two CLI options to assist in checking the deployments: <code>--wait</code> and <code>--timeout</code>. When using <code>--wait</code>, Helm will wait until a minimum expected number of Pods in the deployment are launched before marking the release as successful. Helm will wait as long as what is set with <code>--timeout</code>.</p>
<p>Also, please note that this is not a full list of cli flags. To see a description of all flags, just run <code>helm &lt;command&gt; --help</code>.</p>
<p>If you want to check why your chart might have failed you can use the <a href="https://helm.sh/docs/helm/helm_history/" rel="nofollow noreferrer"><code>helm history</code> command</a>.</p>
