Issues with Multiple Components of Kubernetes Crashing

[jkuruzovich]

After creating the resource group cluster using AKS, multiple core processes including the dashboard are in the CrashLoopBackOff state.

NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system heapster-553147743-tl502 2/2 Running 0 6h
kube-system kube-dns-v20-1654923623-1bw3h 3/3 Running 0 6h
kube-system kube-dns-v20-1654923623-c7xx9 3/3 Running 0 6h
kube-system kube-proxy-jq2lf 1/1 Running 0 6h
kube-system kube-svc-redirect-pqgx7 0/1 CrashLoopBackOff 77 6h
kube-system kubernetes-dashboard-3427906134-vxlgv 0/1 CrashLoopBackOff 83 6h
kube-system tunnelfront-rqm8f 0/1 CrashLoopBackOff 77

Attempts to install tiller have not worked. Using helm 2.6.1

kubectl --namespace kube-system create sa tiller
kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
helm init --service-account tiller
helm init --service-account tiller --upgrade

Executing helm version:
 helm version
Client: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}
Error: cannot connect to Tiller

[evillgenius75]

Same issue here in both westus2 and ukwest regions

[jkuruzovich]

Yes, I was in Westus2. Good to here it wasn't just me. ;) I think those are the only two regions that have availability.

[anhowe]

related to #2

[jkuruzovich]

Thanks! OK. I'll close this issue.