<p>Running helm install for my chart gives my time out error. I have no idea why. Running this in a simple aws instance, no firewall or anything like that. I worked previously and suddenly stopped working.</p>
<pre><code># helm install xxxx-services-1 chart/ --values chart/values.yaml
Error: failed pre-install: timed out waiting for the condition
</code></pre>
<p>already tried:</p>
<ol>
<li>restarting kubernetes</li>
<li>rebooting the machine</li>
<li>kubeadm reset &amp; kubeadm init</li>
</ol>
<p>Update:</p>
<ol>
<li><p>using helm 3</p>
</li>
<li><p>when I run with --debug, these are last lines, and it's stuck there:</p>
<p>client.go:463: [debug] Watching for changes to Job xxxx-services-1-ingress-nginx-admission-create with timeout of 5m0s</p>
<p>client.go:491: [debug] Add/Modify event for xxxx-services-1-ingress-nginx-admission-create: ADDED</p>
<p>client.go:530: [debug] xxxx-services-1-ingress-nginx-admission-create: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:491: [debug] Add/Modify event for xxxx-services-1-ingress-nginx-admission-create: MODIFIED</p>
<p>client.go:530: [debug] xxxxx-services-1-ingress-nginx-admission-create: Jobs active: 1, jobs failed: 0, jobs succeeded: 0</p>
</li>
<li><p>when i do <code>kubectl get jobs</code> i did see an active job, i deleted it, ran the install again - still same result</p>
</li>
</ol>

Moshe Shaham
<p>Found the issue, I didn't taint my master node...</p>
<p><code>kubectl taint nodes --all node-role.kubernetes.io/master-</code></p>
<p>I can't believe how much time I spent on this little thing...</p>
