Kuby can sometimes be attempting to push to old clusters

[lazyatom]

I've noticed this issue while testing Kuby, where I'm frequently creating and destroying clusters -- I believe the implementation here means that kuby tries to use the cached kubeconfig.yaml file, even though the details provided to Kuby's configuration have changed, resulting in the error message Error: Kubernetes cluster unreachable when trying to run kuby setup.

I'd suggest we create a hash of the credentials, and include that into kubeconfig_path somehow, such that any change to the credentials results in an immediate refresh of the Kubernetes configuration.

[camertron]

@lazyatom you're absolutely right, it just looks to see if the kubeconfig file exists, which won't pick up on changes made in your kuby config. I'll file an issue for this.