Skip to content
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 cannot be changed and is not taken into account when Deploying to Kubernetes, new record is not propagated into kube-context in status bar #3910

Closed
odockal opened this issue Sep 14, 2023 · 3 comments
Assignees

Comments

@odockal
Copy link
Contributor

odockal commented Sep 14, 2023

Bug description

I need to restart the podman desktop (or reenable kube context extension) in order to get a new kube context record in.

kube-context-not-updated

Moreover, I cannot switch between different contexts. Also, current kube-context is not applied when I tried to deploy to kubernetes.

kubecontext-broken

Operating system

Windows 10

Installation Method

Other

Version

1.4.0

Steps to reproduce

  1. rm -rf ~/.kube
  2. Start podman desktop
  3. Install Kind
  4. Create kind cluster
  5. ASSERT: kube-context is automatically updated when I create new resource
    Actual result: no kube-context is present upon creation. I need to restart OR manually disable-enable kube-context extension

Relevant log output

No response

Additional context

No response

@odockal odockal changed the title Kube context in status bar is not automatically added when I create new resource (ie. Kind or OS Local) Kube context cannot be changed and is not taken into account when Deploying to Kubernetes, new record is not propagated into kube-context in status bar Sep 15, 2023
@nichjones1 nichjones1 added this to the 1.6.0 milestone Nov 9, 2023
@nichjones1 nichjones1 removed this from the 1.6.0 milestone Nov 29, 2023
@odockal
Copy link
Contributor Author

odockal commented Dec 13, 2023

A little workaround: Restart podman desktop (do not forget to enable close on exit in preferences).

@dgolovin
Copy link
Contributor

dgolovin commented Jun 6, 2024

Could be fixed with #6406.

@dgolovin
Copy link
Contributor

dgolovin commented Jul 2, 2024

It seems fixed, I cannot replicate any of the issues above after starting without ~/.kube folder and starting OpenShift Local. The context status shows up and everything works as expected.

@dgolovin dgolovin closed this as completed Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✔️ Done
Development

No branches or pull requests

3 participants