You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I need to restart the podman desktop (or reenable kube context extension) in order to get a new kube context record in.
Moreover, I cannot switch between different contexts. Also, current kube-context is not applied when I tried to deploy to kubernetes.
Operating system
Windows 10
Installation Method
Other
Version
1.4.0
Steps to reproduce
rm -rf ~/.kube
Start podman desktop
Install Kind
Create kind cluster
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
The text was updated successfully, but these errors were encountered:
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
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.
Bug description
I need to restart the podman desktop (or reenable
kube context
extension) in order to get a new kube context record in.Moreover, I cannot switch between different contexts. Also, current kube-context is not applied when I tried to deploy to kubernetes.
Operating system
Windows 10
Installation Method
Other
Version
1.4.0
Steps to reproduce
rm -rf ~/.kube
Actual result: no kube-context is present upon creation. I need to restart OR manually disable-enable
kube-context
extensionRelevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: