Error: could not find a ready tiller pod

$ kubectl get pods -n kube-system
NAME                             READY   STATUS    RESTARTS   AGE
aws-node-nw2z7                   1/1     Running   0          82m
coredns-dcc5cb8c4-628wg          1/1     Running   0          86m
coredns-dcc5cb8c4-bxhxb          1/1     Running   0          86m
kube-proxy-d87gb                 1/1     Running   0          82m
tiller-deploy-7dd4495c74-5n8xc   0/1     Pending   0          4m3s

$ kubectl get event -n kube-system
LAST SEEN   TYPE      REASON              OBJECT                                MESSAGE
87s         Warning   FailedScheduling    pod/tiller-deploy-7dd4495c74-5n8xc    0/1 nodes are available: 1 Insufficient pods.
4m28s       Normal    SuccessfulCreate    replicaset/tiller-deploy-7dd4495c74   Created pod: tiller-deploy-7dd4495c74-5n8xc
4m28s       Normal    ScalingReplicaSet   deployment/tiller-deploy              Scaled up replica set tiller-deploy-7dd4495c74 to 1

$ eksctl scale nodegroup --cluster=prod --nodes=3 --name=standard-workers
[ℹ]  scaling nodegroup stack "eksctl-prod-nodegroup-standard-workers" in cluster eksctl-prod-cluster
[ℹ]  scaling nodegroup, desired capacity from 1 to 3, max size from 2 to 3

$ kubectl get pods -n kube-system
NAME                             READY   STATUS    RESTARTS   AGE
aws-node-km2gh                   1/1     Running   0          41s
aws-node-nw2z7                   1/1     Running   0          86m
aws-node-vpbd6                   1/1     Running   0          41s
coredns-dcc5cb8c4-628wg          1/1     Running   0          91m
coredns-dcc5cb8c4-bxhxb          1/1     Running   0          91m
kube-proxy-4xglk                 1/1     Running   0          41s
kube-proxy-d87gb                 1/1     Running   0          86m
kube-proxy-wmsgj                 1/1     Running   0          41s
tiller-deploy-7dd4495c74-5n8xc   1/1     Running   0          8m12s