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

Deprecate ByteDance operator and move to unified one #19

Merged
merged 1 commit into from
Sep 10, 2021

Conversation

Jeffwan
Copy link
Collaborator

@Jeffwan Jeffwan commented Sep 10, 2021

Address #17

Community has decided to move to unified golang ray operator and different companies won't maintain their own implementation later. See issue #17 for more details.

Signed-off-by: Jiaxin Shan [email protected]

Community has decided to move to unified golang ray operator and different companies won't maintain their own implementation later. See issue ray-project#17 for more details.

Signed-off-by: Jiaxin Shan <[email protected]>
@Jeffwan
Copy link
Collaborator Author

Jeffwan commented Sep 10, 2021

/cc @chaomengyuan @akanso @chenk008

@chaomengyuan
Copy link
Contributor

LGTM.

@Jeffwan
Copy link
Collaborator Author

Jeffwan commented Sep 10, 2021

Since this change is only related to Bytedance code base and engineer from internal has reviewed it. I will just merge it.

@Jeffwan Jeffwan merged commit 79d4843 into ray-project:master Sep 10, 2021
@Jeffwan Jeffwan deleted the deprecate_bytedance branch September 10, 2021 18:05
lowang-bh pushed a commit to lowang-bh/kuberay that referenced this pull request Sep 24, 2023
Community has decided to move to unified golang ray operator and different companies won't maintain their own implementation later. See issue ray-project#17 for more details.

Signed-off-by: Jiaxin Shan <[email protected]>
sutaakar pushed a commit to sutaakar/kuberay that referenced this pull request Nov 15, 2024
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