panic: runtime error: invalid memory address or nil pointer dereference about kube-no-trouble HOT 4 CLOSED

Hi @san360 thanks for reporting this. I'll certainly try to look into this, but tbh. it might take some time, I'm not familiar with WSL at all ;). Are you able to try with WSL2 - partially out of curiosity on my side, no idea if that might help, but my colleague mentioned there were many improvements/bugfixes since the WSL1.

As a workaround, I would suggest you try to use docker image. We're not publishing it anywhere yet (tbd soon), but just recently added it to the repo, so just building the image from Dockerfile in the root of this repo should work.

from kube-no-trouble.

I have the same error, in mac osx and version 0.3.0 and I think is due to a bad kube config, so I've created a PR to avoid the panic and the error is showing up like:

> ./bin/kubent                                                                                                                                                                                (use1-test-4/default)
3:32PM INF >>> Kube No Trouble `kubent` <<<
3:32PM INF version dev (git sha dev)
3:32PM INF Initializing collectors and retrieving data
3:32PM ERR Failed to initialize: <nil> error="invalid configuration: [context was not found for specified context: test-cluster, cluster has no server defined]"
3:32PM ERR Failed to initialize: <nil> error="invalid configuration: [context was not found for specified context: test-cluster, cluster has no server defined]"
3:32PM ERR Failed to initialize: <nil> error="invalid configuration: [context was not found for specified context: test-cluster, cluster has no server defined]"
3:32PM INF Loaded ruleset name=deprecated-1-16.rego
3:32PM INF Loaded ruleset name=deprecated-1-22.rego

from kube-no-trouble.

@san360 this should be resolved, would you be able to test latest master on windows to confirm?

from kube-no-trouble.

I believe this has been resolved, as per above, and covered by tests as well. Closing this issue. In case you experience the same again please comment and we can reopen.

from kube-no-trouble.