Describe the bug
It would appear this bug has arisen as a result of the most recent changes adding the logic for detecting connectivity with the k8s API server. More specifically, this has to do with the DialTimeout call that is made. It should be noted that currently for my setup, communication is achieved to the k8s API-server via rancher's proxy. Based on the code changes I can't imagine this has any impact but it's worth noting nonetheless.

To Reproduce
Steps to reproduce the behavior:

1. Open k9s session
2. Enter a pod shell
3. Exit from the container
4. Attempt to display the YAML or Describe the pod (may take a few tries)
5. K9s should terminate the current session

Expected behavior
The session should not be terminated as there was not a connection lost to the api-server

Screenshots

Versions (please complete the following information):

• OS: OSX Mojave
• K9s: 0.12.0
• K8s: 1.15.5