2.0.1: API - Deleting an AWS cluster throws Helm errors in logs

[eldridgeh]

Short Summary: After deleting an AWS cluster, helm errors are thrown in the SG log. Steps to Reproduce:

1. Create a cluster
2. After it has spun up, delete the cluster Expected Results: The cluster is deleted without any errors in the SG logs. We may need to delete apps first before we delete the instance. Actual Results: Errors, horrible, horrible errors Dev Info: (add links to log files)
3. Output of go version: 1.10
4. Commit hash or release tag used (git log): d3d9490a7ba956537873518e1198eccfeb003189
5. Number of Masters and Nodes: Any
6. Cloud Provider: AWS

E1207 18:45:12.186227   27632 portforward.go:178] lost connection to pod
ERRO[2018-12-07T18:45:12-06:00] helm: list releases: 04af46ec cluster: list releases: rpc error: code = Unavailable desc = transport is closing 
ERRO[2018-12-07T18:45:14-06:00] helm: list releases: 04af46ec cluster: list releases: get tiller pod: Get https://13.250.5.42/api/v1/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: unexpected EOF 
ERRO[2018-12-07T18:45:15-06:00] helm: list releases: 04af46ec cluster: list releases: get tiller pod: Get https://13.250.5.42/api/v1/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp 13.250.5.42:443: connect: connection refused 
ERRO[2018-12-07T18:45:15-06:00] helm: list releases: 04af46ec cluster: list releases: get tiller pod: Get https://13.250.5.42/api/v1/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp 13.250.5.42:443: connect: connection refused 
ERRO[2018-12-07T18:45:15-06:00] helm: list releases: 04af46ec cluster: list releases: get tiller pod: Get https://13.250.5.42/api/v1/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp 13.250.5.42:443: connect: connection refused 

[eldridgeh]

This still happens