[Bug]: Changing the kube context between crc and other provider (kind) via Podman Desktop triggers unwanted start of the OS local cluster

crc-org / crc-extension

Red Hat OpenShift Local Extension for integration of OpenShift Local clusters with Podman Desktop

Apache License 2.0

17 stars 19 forks source link

[Bug]: Changing the kube context between crc and other provider (kind) via Podman Desktop triggers unwanted start of the OS local cluster #153

Closed odockal closed 1 year ago

odockal commented 1 year ago

Env: Red Hat OpenShift Local (user) v1.0.3, Podman Desktop 1.1.0, Fedora 37 and Windows 10 Pro. I had this strange behavior happening when testing openshift local. I have installed os local, started the openshift preset. Deployed the app, tested. I have also installed another providers like kind and dev sandbox, thus I have multiple kube context available. I have stopped the openshift local. Switched between contexts and returned back to crc-admin, which triggered os local start up.

crc-autostart-bug

jeffmaury commented 1 year ago

Closing as it was a Podman Desktop issue in the dashboard fixed then