<p>After months of using Helm (version 2.6.2) to deploy services in kubernetes, we've started experiencing random errors while performing the <code>--upgrade</code> command.</p>

<p>Most of the time the upgrade times out, in other situations instead it looks like a network issue occurs, with errors like <code>getsockopt: connection refused</code> or <code>TLS handshake timeout</code>.</p>

<p>Sometimes we've also seen <code>the server cannot complete the requested operation at this time, try again later (get configmaps)</code>.</p>

<p>We're using Helm to deploy several versions a day of our services to our CI environment, and the instability of the deployment process that started to creep in is affecting our productivity.</p>

<p>Any idea what I should look for to restore the <code>--upgrade</code> command to a reliable state?</p>

<p>Upgrading to Helm 2.7.0 and using <code>--history-max</code> solved the issue for me, so the problem must have been related to the fact that old config maps were not cleared up by tiller, and over time they piled up until tiller started to struggle to make sense of them. </p>

<p>More information about it <a href="https://blog.shazam.com/rewriting-history-with-helm-b66e72958008" rel="nofollow noreferrer">here</a>. </p>
