Open romilbhardwaj opened 11 months ago
This is also related to #3013
Going to self-assign and work on this!
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
I often terminate a Kubernetes cluster externally using the cloud console/cli (e.g.,
gcloud container clusters delete <cluster-name> --region us-central1-c
), but I forget to run sky check to update the list of enabled clouds.As a result, the next
sky launch
fails:We should consider printing a warning and continuing by either: 1) Excluding
Kubernetes
from the list of clouds considered by the optimizer 2) RemovingKubernetes
from the list of enabled clouds stored in global user state.1 is less aggressive and doesn't require user to re-run
sky check
in case it is a transient failure.