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

add standard label for the filtering of cluster #342

Merged

Conversation

scarlet25151
Copy link
Collaborator

Why are these changes needed?

Related issue number

#338

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

@Jeffwan
Copy link
Collaborator

Jeffwan commented Jul 6, 2022

I create #338 for other reason. I will cut a PR to add labels to manifest.
I think what you need to do here is to make sure apiserver just filter out the cluster with some label like app.kubernetes.io/managed-by=kuberay-apiserver

ray-operator/controllers/ray/common/constant.go Outdated Show resolved Hide resolved
ray-operator/controllers/ray/common/constant.go Outdated Show resolved Hide resolved
ray-operator/controllers/ray/common/ingress.go Outdated Show resolved Hide resolved
@scarlet25151 scarlet25151 force-pushed the enhancement/add-standard-label branch 2 times, most recently from 7b58d6c to 18acf6c Compare July 6, 2022 21:12
@Jeffwan
Copy link
Collaborator

Jeffwan commented Jul 6, 2022

@scarlet25151 I have some more comments on the naming, please address them

@scarlet25151 scarlet25151 force-pushed the enhancement/add-standard-label branch from 18acf6c to 2242085 Compare July 6, 2022 22:02
@Jeffwan
Copy link
Collaborator

Jeffwan commented Jul 6, 2022

It looks good to me now

@Jeffwan Jeffwan merged commit 15cdd55 into ray-project:master Jul 6, 2022
lowang-bh pushed a commit to lowang-bh/kuberay that referenced this pull request Sep 24, 2023
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.

2 participants