-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Plugins load failed!" when no current context #2651
Comments
Happens to me as well, both with and without plugins. It seems to block me from choosing context for ~5 seconds with the following error: "😡 no connection to cached dial". Does not happen with |
Encountering the exact same problem as Emil, on K9s v0.32.4 and K8s v1.29.1. |
I've also been encountering this issue. If I set a context explicitly prior to opening k9s, it's fine but I cannot switch to another context while in k9s without it breaking. |
Another way to reproduce this is:
Not only does this issue prevent you from selecting a context, but is also the cause of another long standing issue I've had that We don't want to set a context (
We thenhave a standalone config file per cluster, joined together in
This all works 100% fine with Also tested by wiping out Here's the full logs (
|
i have this issue too |
I got around my issue by specifying the context's namespace I had access to in my kube-config. I was not allowed to see all namespaces, but limiting it to a specific solved it. |
when we have mutiple cluster, we couldnt limit to specific namespace |
When loading plugins, skip loading context-aware configurations if there is no current context (i.e. when `current-context` in the kubeconfig is empty).
The issue seems to be at the point where k9s tries to load plugins based on the context when said context is empty. I gave a PR a shot by just ignoring the loading of plugins from the context-based directory if the context comes empty. |
Im also having this exact same issue |
One additional situation that brings this up is when the |
we are running k9s inside an container. In our case, there is no kubeconfig, only the in-cluster config. It works months ago (until 0.29), but now it seems broken. |
Facing the same on arch, kubernetes v1.28.2, k9s: v0.32.4 |
Observing this issue for one of the context, rest all context works well |
FWIW, I was having a similar issue this morning after putting my mac to sleep with multiple k9s running last week, and the local namespace config.yaml had some trash appended to the end of the file. Once I fixed the config yaml it was fine, and I discovered this by viewing the namespaces in the context, and when I tried to "use" the namespace I was after, it said it was missing a ":" on line 20, which was the end of the file, where I found some trash (part of the word "localhost", but without the "loc" at the start). So, perhaps unrelated, but may have some issue with multiple k9s instances viewing the same namespace saving the config on shutdown when the machine goes idle/sleep. |
This issue appeared to me when I decided to rename my initially given deafult context names into something more meaninful for me. After k9s restart, the issue appeared. What I found interesting is when I opened my When I manually defined the Additionally, like it was previously said, it would be sweet to have also no definition of context so that you basically need to choose one right from the start without any problems (some flag in k9s config.yaml file). |
I fixed this by exporting the config file to the native Kubernetes path |
This seems only to be a problem in k9s version 0.32.5. I had the same issue and fixed it with a roll back to k9s version 0.31.5. After that it worked just fine without setting a |
the error related to the current-context section, the current context is set but k9s can not find this context (the context is renamed or deleted). So the way to work is set different default context by command |
Describe the bug
When starting
k9s
without a current context set, there's an error telling me that Plugins load failed!. But when having a current context set, or specifying the --context flag when starting k9s, it works as expected. I have no plugins.To Reproduce
Historical Documents
k9s logs:
Expected behavior
I'll end up in the k9s context meny with no error.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: