Kube context is not loaded in podman desktop until restart

[odockal]

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

0. Make sure to remove any kubeconfig file beforehand. rm -rf ~/.kube
1. Start up podman desktop
2. Crate and start podman machine
3. Download Kind/Minikube or install dev sandbox
4. Create a kind cluster (or any other that touches ~/.kube/config and add new kube context)
5. Assert: New kube context is available in the Podman Desktop
   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.

[feloy]

related to #6307

[cdrage]

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.

[jeffmaury]

Cannot reproduce using 1.10.0-next

[odockal]

@jeffmaury Cleaned up all the machine. hit this again, except with OpenShift Local adjusted kubeconfig.

[odockal]

Disable+enable of Kube-context extension did the job though.

[feloy]

@odockal I cannot reproduce the issue on Windows 11 with Podman Desktop v1.10.2

Is it reproducible on your side with this version?

[odockal]

@feloy It is reproducible with 1.10.3 as well. I have update steps to reproduce.

[feloy]

Thanks @odockal. The trick was to remove the parent directory (.kube/), not only the kubeconfig file, as noticed by @axel7083 in containers/podman-desktop-extension-ai-lab#1135, but I was only removing the kubeconfig file.

I tested by removing the parent directory, and it is effectively reproducible. I'll make a fix

[odockal]

@feloy Great! It is always the best to have the very precise steps to reproduce. Thanks!