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
We should consider suppressing warnings when the Kubernetes cluster is no longer reachable (e.g., after GKE cluster has been deleted or docker runtime is not running for sky local up). Currently, we get warnings like:
sky show-gpus --cloud kubernetes
WARNING:urllib3.connectionpool:Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x1075c3af0>, 'Connection to 146.148.51.187 timed out. (connect timeout=5)')': /api/v1/namespaces/default/pods
WARNING:urllib3.connectionpool:Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x1075c3c10>, 'Connection to 146.148.51.187 timed out. (connect timeout=5)')': /api/v1/namespaces/default/pods
WARNING:urllib3.connectionpool:Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x1075c3730>, 'Connection to 146.148.51.187 timed out. (connect timeout=5)')': /api/v1/namespaces/default/pods
No GPUs found in Kubernetes cluster. If your cluster contains GPUs, make sure nvidia.com/gpu resource is available on the nodes and the node labels for identifying GPUs (e.g., skypilot.co/accelerator) are setup correctly. To further debug, run: sky check.
The text was updated successfully, but these errors were encountered:
We should consider suppressing warnings when the Kubernetes cluster is no longer reachable (e.g., after GKE cluster has been deleted or docker runtime is not running for
sky local up
). Currently, we get warnings like:The text was updated successfully, but these errors were encountered: