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

[Bug] label rayNodeType is useless #698

Merged
merged 6 commits into from
Nov 9, 2022

Conversation

kevin85421
Copy link
Member

@kevin85421 kevin85421 commented Nov 8, 2022

Why are these changes needed?

Label rayNodeType is useless in the whole KubeRay operator. I guess people are trying to add the label ray.io/node-type which will be set by the Kuberay operator.

metadata:
labels:
# custom labels. NOTE: do not define custom labels start with `raycluster.`, they may be used in controller.
# Refer to https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
rayCluster: raycluster-sample # will be injected if missing
rayNodeType: head # will be injected if missing, must be head or wroker
groupName: headgroup # will be injected if missing

RayNodeTypeLabelKey = "ray.io/node-type"

Related issue number

Closes #679

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(
  • For RayCluster YAMLs in ray-operator/config/samples, I used the configuration test framework to test them.

    cd tests/framework
    python3 test_sample_raycluster_yamls.py 2>&1 | tee log

    Screen Shot 2022-11-07 at 11 59 15 PM

  • ray_v1alpha1_rayjob.yaml: I tested it by following the rayjob.md.

  • ray_v1alpha1_rayservice.yaml: I tested it by following the rayservice.md. I faced a bug mentioned by a user in KubeRay slack channel (thread) and solved it by setting SERVE_DEPLOYMENT_HANDLE_IS_SYNC (solution from @shrekris-anyscale).

  • rayjob_controller_test.go, rayservice_controller_test.go, rayjob_types_test.go, rayservice_types_test.go: Use make build to test them.

  • I tested the helm chart.

@kevin85421 kevin85421 marked this pull request as ready for review November 8, 2022 20:00
@kevin85421
Copy link
Member Author

@shrekris-anyscale can you help me review the changes in ray_v1alpha1_rayservice.yaml? Thank you!
@Jeffwan can you help me review the changes in config/prometheus/podMonitor.yaml and docs/guidance/observability.md? I am not familiar with that parts. Thank you!
@DmitriGekhtman can you help me review this PR? Thank you!

Copy link
Contributor

@shrekris-anyscale shrekris-anyscale left a comment

Choose a reason for hiding this comment

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

Nice work so far! I left a comment for the ray_v1alpha1_rayservice.yaml file.

ray-operator/config/samples/ray_v1alpha1_rayservice.yaml Outdated Show resolved Hide resolved
@Jeffwan
Copy link
Collaborator

Jeffwan commented Nov 8, 2022

It looks good to me. Have you check all rayNodeType references? Let's make sure they are totally cleaned up.

@kevin85421
Copy link
Member Author

kevin85421 commented Nov 9, 2022

Have you check all rayNodeType references? Let's make sure they are totally cleaned up.

Thank @Jeffwan for your review! I have checked all occurrences of rayNodeType in KubeRay with the search functionality provided by VSCode. Only pod.go has some variables with the name "rayNodeType" (not pod labels). Thank you!

@DmitriGekhtman DmitriGekhtman merged commit 17264a6 into ray-project:master Nov 9, 2022
lowang-bh pushed a commit to lowang-bh/kuberay that referenced this pull request Sep 24, 2023
The label rayNodeType is not used in the KubeRay operator code. This PR removes the label from all sample configs.
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.

[Bug] label rayNodeType is useless
4 participants