<p>I'm new to Kubernetes and Helm. I have installed k3d and helm:
k3d version v1.7.0
k3s version v1.17.3-k3s1</p>
<pre><code>helm version
version.BuildInfo{Version:&quot;v3.2.4&quot;, GitCommit:&quot;0ad800ef43d3b826f31a5ad8dfbb4fe05d143688&quot;, GitTreeState:&quot;clean&quot;, GoVersion:&quot;go1.13.12&quot;}
</code></pre>
<p>I do have a cluster created with 10 worker nodes. When I try to install stackstorm-ha on the cluster I see the following issues:</p>
<pre><code>helm install stackstorm/stackstorm-ha --generate-name --debug
client.go:534: [debug] stackstorm-ha-1592860860-job-st2-apikey-load: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: failed post-install: timed out waiting for the condition
helm.go:84: [debug] failed post-install: timed out waiting for the condition
njbbmacl2813:~ gangsh9$ kubectl get pods
Unable to connect to the server: net/http: TLS handshake timeout
</code></pre>
<p>kubectl describe pods either shows :</p>
<pre><code>Events:
  Type     Reason     Age                 From                             Message
  ----     ------     ----                ----                             -------
  Normal   Scheduled  &lt;unknown&gt;           default-scheduler                Successfully assigned default/stackstorm-ha-1592857897-st2api-7f6c877b9c-dtcp5 to k3d-st2hatest-worker-5
  Warning  Failed     23m                 kubelet, k3d-st2hatest-worker-5  Error: context deadline exceeded
  Normal   Pulling    17m (x5 over 37m)   kubelet, k3d-st2hatest-worker-5  Pulling image &quot;stackstorm/st2api:3.3dev&quot;
  Normal   Pulled     17m (x5 over 28m)   kubelet, k3d-st2hatest-worker-5  Successfully pulled image &quot;stackstorm/st2api:3.3dev&quot;
  Normal   Created    17m (x5 over 28m)   kubelet, k3d-st2hatest-worker-5  Created container st2api
  Normal   Started    17m (x4 over 28m)   kubelet, k3d-st2hatest-worker-5  Started container st2api
  Warning  BackOff    53s (x78 over 20m)  kubelet, k3d-st2hatest-worker-5  Back-off restarting failed container
</code></pre>
<p>or</p>
<pre><code>Events:
  Type     Reason     Age                    From                             Message
  ----     ------     ----                   ----                             -------
  Normal   Scheduled  &lt;unknown&gt;              default-scheduler                Successfully assigned default/stackstorm-ha-1592857897-st2timersengine-c847985d6-74h5k to k3d-st2hatest-worker-2
  Warning  Failed     6m23s                  kubelet, k3d-st2hatest-worker-2  Failed to pull image &quot;stackstorm/st2timersengine:3.3dev&quot;: rpc error: code = Unknown desc = failed to pull and unpack image &quot;docker.io/stackstorm/st2timersengine:3.3dev&quot;: failed to resolve reference &quot;docker.io/stackstorm/st2timersengine:3.3dev&quot;: failed to authorize: failed to fetch anonymous token: Get https://auth.docker.io/token?scope=repository%3Astackstorm%2Fst2timersengine%3Apull&amp;service=registry.docker.io: net/http: TLS handshake timeout
  Warning  Failed     6m23s                  kubelet, k3d-st2hatest-worker-2  Error: ErrImagePull
  Normal   BackOff    6m22s                  kubelet, k3d-st2hatest-worker-2  Back-off pulling image &quot;stackstorm/st2timersengine:3.3dev&quot;
  Warning  Failed     6m22s                  kubelet, k3d-st2hatest-worker-2  Error: ImagePullBackOff
  Normal   Pulling    6m10s (x2 over 6m37s)  kubelet, k3d-st2hatest-worker-2  Pulling image &quot;stackstorm/st2timersengine:3.3dev&quot;
</code></pre>
<p>Kind of stuck here.</p>
<p>Any help would be greatly appreciated.</p>

<p>The <code>TLS handshake timeout</code> error is very common when the machine that you are running your deployment on is running out of resources.  Alternative issue is caused by slow internet connection or some proxy settings but we ruled out that since you can pull and run docker images locally and deploy small nginx webserver in your cluster.</p>
<p>As you may notice in the <code>stackstorm</code> helm chart it installs a big amount of services/pods inside your cluster which can take up a lot of resources.</p>
<blockquote>
<p>It will install 2 replicas for each component of StackStorm
microservices for redundancy, as well as backends like RabbitMQ HA,
MongoDB HA Replicaset and etcd cluster that st2 replies on for MQ, DB
and distributed coordination respectively.</p>
</blockquote>
<p>I deployed <code>stackstorm</code> on both k3d and GKE but I had to use fast machines in order to deploy this quickly and successfully.</p>
<pre><code>NAME: stackstorm
LAST DEPLOYED: Mon Jun 29 15:25:52 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
Congratulations! You have just deployed StackStorm HA!
</code></pre>
