Initial cluster check failure could be more helpful

[dsyer]

$ telepresence list
telepresence: error: connector.Connect: initial cluster check failed: Get "https://dsyer-tap-demo-mskfvjde.hcp.eastus.azmk8s.io:443/version": dial tcp: lookup dsyer-tap-demo-mskfvjde.hcp.eay

See logs for details (2 errors found): "/home/dsyer/.cache/telepresence/logs/daemon.log"

See logs for details (3 errors found): "/home/dsyer/.cache/telepresence/logs/connector.log"
If you think you have encountered a bug, please run `telepresence gather-logs` and attach the telepresence_logs.zip to your github issue or create a new one: https://github.com/telepresence.

The cluster is no longer accessible (it was destroyed on AKS by a reaper agent that I don't control), so I understand the problem, but

a) the error isn't very helpful - it could just tell me in plain language that the current cluster isn't accessible
b) the only way I know to fix it is to manually delete the ~/.cache/telepresence (if that's the right thing to do maybe telepresence should tell me so, or offer to do it for me)

[thallgren]

@dsyer why is this fixed by removing the cache? AFAIK, telepresence will try and access the same cluster regardless because it uses your kubeconfig, and the kubeconfig is not in the cache.

[dsyer]

I forget. I think maybe when the cache was removed I got a more sensible error message. I was able to debug and make progress anyway.