skypilot-org
[k8s][ux] Auto-exclude stale Kubernetes cloud
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:
sky.exceptions.ResourcesUnavailableError: Timed out when trying to get node info from Kubernetes cluster. Please check if the cluster is healthy and retry.
We should consider printing a warning and continuing by either:
- Excluding
Kubernetesfrom the list of clouds considered by the optimizer - Removing
Kubernetesfrom 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.
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.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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 was closed because it has been stalled for 10 days with no activity.
I'm running into this after having renewed my k8s cert in my kube config. I can see the pods as unhealthy, there might have been another isuse.
However, I'm unable to start new clusters on said k8s due this error.
Update
It seems like the error is actually swallowing a real error - in my case BAD_BASE64_DECODE - which in my case I can only see when executing the purge command
Thanks for the report @chris-aeviator - that sounds bad. Can you share the full output log and the commands you ran so I can reproduce it?
Nvm @chris-aeviator, I can reproduce this. Looks like a recent regression from #4443. Being fixed in https://github.com/skypilot-org/skypilot/pull/4514 - can you give that branch a try and see if it fixes your issue too?
