Closed duplabe closed 9 months ago
@duplabe Thank you for this report! Could you include k9s debug logs? Tx!
@derailed I've added the logs.
Additional info: I usually clear my current-context
with kubectx -u
to prevent any accidental change on my clusters. I only get the error I reported when the current-context
is empty.
Eg.:
$ kubectx k8s
Switched to context "k8s".
$ k9s --context k8s
# starting without error
$ kubectx -u
Unsetting current context.
Property "current-context" unset.
$ k9s --context k8s
____ __.________
| |/ _/ __ \______
| < \____ / ___/
| | \ / /\___ \
|____|__ \ /____//____ >
\/ \/
Boom!! runtime error: invalid memory address or nil pointer dereference.
$ kubectx ip-dev
Switched to context "ip-dev".
$ k9s --context k8s
# starting without error, with the k8s context
$ kubectx -u
Unsetting current context.
Property "current-context" unset.
$ k9s
# starting without error, and with the context selector
$ k9s --context k8s
____ __.________
| |/ _/ __ \______
| < \____ / ___/
| | \ / /\___ \
|____|__ \ /____//____ >
\/ \/
Boom!! runtime error: invalid memory address or nil pointer dereference.
I tried 0.30.4 and looks like https://github.com/derailed/k9s/pull/2386 solved this issue also, so I'm closing this. Thanks!
Describe the bug Starting k9s with a valid kubeconfig context (
--context
) givesBoom!! runtime error: invalid memory address or nil pointer dereference.
To Reproduce Steps to reproduce the behavior:
Expected behavior
Start k9s with the given context. Starting without the
--context
param works as expected.Versions (please complete the following information):
Additional context This bug came up with the 0.30.0 update
Logs: