-
Notifications
You must be signed in to change notification settings - Fork 294
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
Kube context is not loaded in podman desktop until restart #6406
Comments
related to #6307 |
Encountered the same issue today, and with the included fix of #6307 Mine was the fact that the Kubernetes dashboard sections did not appear until restart either. |
Cannot reproduce using 1.10.0-next |
@jeffmaury Cleaned up all the machine. hit this again, except with OpenShift Local adjusted kubeconfig. |
Disable+enable of Kube-context extension did the job though. |
@odockal I cannot reproduce the issue on Windows 11 with Podman Desktop v1.10.2 Is it reproducible on your side with this version? |
@feloy It is reproducible with 1.10.3 as well. I have update steps to reproduce. |
Thanks @odockal. The trick was to remove the parent directory ( I tested by removing the parent directory, and it is effectively reproducible. I'll make a fix |
@feloy Great! It is always the best to have the very precise steps to reproduce. Thanks! |
Bug description
I have no
~/.kube/config
file, thus not kube context available. I install DevSandbox extension in Podman Desktop and create a dev-sandbox resource (aka logging in and getting oc login command). At this moment I have my~/.kube.config
filled with information about dev sandbox cluster and technically can connect to it. Podman Desktop has not information about the context until I restart it, then it works.Operating system
Windows 10, 11
Installation Method
Installer from website/GitHub releases
Version
1.8.0
Steps to reproduce
rm -rf ~/.kube
Actual result: No kube context added. Only after restart or reenblement of the kube-context extension
Relevant log output
No response
Additional context
Kind and minikube could have the same problem, I believe.
The text was updated successfully, but these errors were encountered: