v0.31.4 - panic; no client connection detected

[jmsariron]

Describe the bug
Can't start K9s, getting the error attached on the screenshots section

To Reproduce
Steps to reproduce the behavior:

Execute k9s

Screenshots

Versions (please complete the following information):

• OS: Fedora Linux
• K9s: 0.31.4
• K8s: I dont have a default context set

Additional context
Running fine with v0.30.8
I've tried deleting the $HOME/.config/k9s dir when launching the app just to make sure there is nothing there conflicting.

[humanumbrella]

+1

OS: macOS Sonoma 14.2.1
K9s: 0.31.4

was fine with v0.30.8

I noticed a new config.yaml vs config.yml -- but messing with that hasn't fixed the issue.

[jmsariron]

Edited the OP with the following:

I've tried deleting the $HOME/.config/k9s dir when launching the app just to make sure there is nothing there conflicting.

[humanumbrella]

perhaps the fixes from #2464 weren't fully adequate

also, this issue might shed more light --> #2463

[jmsariron]

Looking at that issue, looks a bit like my case, no default context selected, when I open K9s (With 0.30.8) it brings the context selector view. Is this no longer supported on 0.31?

[humanumbrella]

Looking at that issue, looks a bit like my case, no default context selected, when I open K9s (With 0.30.8) it brings the context selector view. Is this no longer supported on 0.31?

🤷‍♂️ - was just attempting to find a quick fix ... i'm gonna go back to 0.30.8 for now

[kazeshini178]

@humanumbrella thanks looking at #2463 help my side.

I managed to run k9s --logLevel debug --logFile k9s_0.31.4.log, then looking at the log file I found the same error in the above logged issue.
If I remove the fullScreenLogs prop and run k9s it seems to run. Possible this property has been replaced or removed in the latest version.

Once that was removed k9s seems to run again.

[mydoomfr]

@humanumbrella thanks looking at #2463 help my side.

I managed to run k9s --logLevel debug --logFile k9s_0.31.4.log, then looking at the log file I found the same error in the above logged issue. If I remove the fullScreenLogs prop and run k9s it seems to run. Possible this property has been replaced or removed in the latest version.

Once that was removed k9s seems to run again.

+1
Removing the fullScreenLogs property seems to fix the issue. Thanks!

OS: macOS Sonoma 14.2.1
K9s: 0.31.4

[torbjornvatn]

Same here

[flamadrid-jsmdg]

The reasons I have the "panic: no client connection detected" in my case is because I don't specify a context at start up, but that should be possible, at least it was. Launching it with k9s --context some-context works

[mingzaily]

Same here
Deleted $HOME/.config/k9s

OS: macOS Sonoma 14.2.1
K9s: 0.31.4

[torbjornvatn]

I see that the "recreated" config.yaml has a fullScreen: false instead of fullScreenLogs: false in the logger: section

[MaxenceG2M]

Hi!

I see that the "recreated" config.yaml has a fullScreen: false instead of fullScreenLogs: false in the logger: section

(If this can help) With the same problem, following @torbjornvatn's remark fix the issue on my side.

[tomdevroomen]

I also experienced this issue on MacOS 14.2.1 updating from 0.30.8 to 0.31.4
For me it was resolved after removing the ~/.k9s-folder and ~/Library/Application Support/k9s/.

[CloudAc]

Same problem here. After removing ~/Library/Application Support/k9s/ it's working as mentioned by @tomdevroomen

[electr0sheep]

I didn't have a ~/.k9s folder, but I did have a ~/.config/k9s folder (k9s info will show you where this is). Removing that fixed the issue for me.

[codelabs]

I just commented fullScreenLogs line in ~/Library/Application Support/k9s/config.yaml and it worked.

[derailed]

Thank you all for tuning in and helping each others out!!

Please take a peek at:
Release notes - Breaking Bad!
Video

[saturn4er]

Hi there, I just removed ~/Library/Application Support/k9s/ directory, and error persists. There's no other logs anywhere for k9s, as I can see

[saturn4er]

I managed to start k9s by passing --context argument. My fault, I broke kubeconfig before

[dlxeon]

Got same error on Windows. Removed ~\AppData\Local\k9s\ and it helped

[jorgecara]

In my case there were two config files one ending on yaml and the other on yml. Removing the old one fixed it:

[arevenes]

Had same issue, removing fullScreenLogs solved it

[anthosz]

Same issue here, tried to remove ~/.config/k9s without success

Edit: fixed, also to be removed: ~/.local/share/k9s

[vakorol]

None of the solutions above worked for me. I had to downgrade to v.0.30.8.

[KulykDmytro]

Had same issue, removing/commenting fullScreenLogs solved it

[derailed]

@vakorol Could you share your details here and what you are experiencing.
We can help you sort this out.
Not to mention, helping other folks as well as this seems to be a problem area.
Thank you!

[0x705h]

Same experience here. I updated k9s from yesterday's release (it was for me 0.31.3) to the current one (0.31.4) and it stopped working.
I've tried all the suggestions in this thread with no avail.
I have the same behaviour as @jmsariron who started this thread.

[davidreis97]

Seems like there is another issue that happens when you try to start k9s without specifying a context:

These are the verbose logs on an m1 Pro:

🐶 K9s starting up...
config refine failed error=unable to activate context "": getcontext - invalid context specified: ""
Fail to load global/context configuration �error= unable to activate context "": getcontext - invalid context specified: ""
No custom skin found. Using stock skin

@derailed I think "AsDesigned" label no longer applies here

[dsiebel]

Experiencing exactly the same after upgrading to 0.31.4 (running MacOS Ventura on M1).

7:08PM INF 🐶 K9s starting up...
7:08PM ERR config refine failed error="unable to activate context \"\": getcontext - invalid context specified: \"\""
7:08PM ERR Fail to load global/context configuration error="unable to activate context \"\": getcontext - invalid context specified: \"\""

Worked around it by creating an alias:

alias k9s='k9s --context rancher-desktop --logoless -c ctx'

Where rancher-desktop could be any valid context from $KUBECONFIG.

[jimleroyer]

Deleting content of the ~\scoop\persist\k9s folder also helps, if you manage your installation via scoop. Thanks for the great tool btw!

[derailed]

You guys are awesome!!
So humbling to see...

Hoping we're happier on v0.31.5?
Crossing fingers and toes...

[dsiebel]

Can confirm it now works perfectly fine. That's one hell a TTR! 🤩

[jmsariron]

issue is closed but also wanted to confirm with 0.31.5 is working fine even without a default context selected.

Thanks a lot! :D