Describe the bug
If K9s is open in a terminal and connected towards a cluster and the cluster is terminated while the k9s terminal is still open - the k9s log file (stored under /tmp/ ) starts to be filled up with a lot of messages regarding "i/o timeout".
As in our setup, our clusters does not persist that long, so many users still have their K9s up in a terminal for days/weeks but lost the connection to the cluster which makes the k9s log file in the /tmp/ to be quite huge!

To Reproduce
Steps to reproduce the behavior:

1. Start K9s in a terminal towards a cluster'
2. Terminalte the cluster
3. Keep the K9s terminal up .
4. Check the K9s log file under /tmp/

Expected behavior
If a cluster is terminated and gone for while and K9s could not connect to that cluster, the K9s should bail out and terminate itself instead of retry forever and fill the K9s log file.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: Linux x86_64
• K9s [e.g. 0.9.3]
• K8s [e.g. 1.15.3]

Additional context
Add any other context about the problem here.