Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[k8s] Suppress warnings when kubernetes cluster is not reachable #3591

Closed
romilbhardwaj opened this issue May 24, 2024 · 0 comments · Fixed by #3674
Closed

[k8s] Suppress warnings when kubernetes cluster is not reachable #3591

romilbhardwaj opened this issue May 24, 2024 · 0 comments · Fixed by #3674
Labels
k8s Kubernetes related items

Comments

@romilbhardwaj
Copy link
Collaborator

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s Kubernetes related items
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant