Bug: Default context cluster name displayed when running with different context

[lackerman]

Firstly, thanks for creating k9s. Although I have had a few issues whilst playing with it, I am very thankful for what you've created.

Steps to reproduce:

Note: you need more than 1 context available (2 different clusters) in your list of contexts. For example serverA/foo & serverB/bar

1. Use kubectl to set your current context, eg:

 kubectl config serverA/foo

2. Start k9s with the --context flag pointing to the other context, eg:

 k9s --context serverB/bar

3. When the view is initialised the ClusterName in the top left will be that of the current kubectl context, not the context passed to k9s

[derailed]

Thanks for the kind words @lackerman. I think this is fixed in 0.1.4. If not please reopen. Tx!!