Boom!! Unauthorized access to namespace "...".

[markusheiden]

Describe the bug
K9S does not start at all. It immediately exists with:
Boom!! Unauthorized access to namespace "...".

To Reproduce
Steps to reproduce the behavior:

1. Start K9S on a cluster with restricted access.
2. See error.

Expected behavior
K9S at least explains which rights are missing.

Versions (please complete the following information):

• OS: OSX 10.14.5
• K9s: 0.6.7
• K8s: Client 1.14.2, Server 1.13.4

Additional context
(Very) early versions of K9S worked fine.

[den-is]

Instead of creating similar issue I will write my additional comments here:

1. I've encountered same Boom!! thing
   solution - I forgot to connect to VPN which grants access to cluster.

Then I've start thinking - What a hell? Why only "Boom!!" - Why error about connection issue can't be more descriptive? And found another issue:
Again text can't be seen in dark theme:

But after selecting line I've got full message:

Boom!! Unauthorized access to namespace "default".

Curious if it is possible to alert message like "Not only unauthorized, but can't connect at all, dude."

[derailed]

@markusheiden @den-is Thank you both for the report! I'll add more info for the namespace issue and Denis will fix the color too ;) on the next drop.

[derailed]

@markusheiden also... tailing the K9s logs should show you the actual access issue.

[derailed]

@markusheiden @den-is Fixed 0.7.0!