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

feat(update): Adding CoreWeave label to identify GPUs in K8s #2650

Merged
merged 4 commits into from
Oct 4, 2023

Conversation

rtalaricw
Copy link
Contributor

@rtalaricw rtalaricw commented Oct 3, 2023

This PR adds:

  • CoreWeaveLabelFormatter to identify GPU nodes within our K8s cluster.
  • Code is formatted using format.sh.

Copy link
Collaborator

@romilbhardwaj romilbhardwaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks @rtalaricw and welcome to SkyPilot! Super excited to have coreweave support. One minor comment, otherwise LGTM.

@@ -304,6 +327,7 @@ def get_gpu_label_key_value(acc_type: str, check_mode=False) -> Tuple[str, str]:
# Check if the cluster has GPU labels setup correctly
label_formatter, node_labels = \
detect_gpu_label_formatter()

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these new lines at L330 and L354 unintended? If so, can we revert them?

@romilbhardwaj romilbhardwaj merged commit dc11e79 into skypilot-org:master Oct 4, 2023
18 checks passed
@rtalaricw rtalaricw deleted the rahul/add_cw_gpu_label branch October 4, 2023 18:01
jc9123 pushed a commit to jc9123/skypilot that referenced this pull request Oct 11, 2023
…org#2650)

* feat(update): Adding CoreWeave label to identify GPUs in K8s

* feat(fix): Remove broken line

* feat(fix): Fixing label_formatter detection

* feat(code): Lint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants