feat: Added kuberay support and consolidated ray initialization #5654
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ntkathole
changed the title
ntkathole
force-pushed
the
codeflare_final
branch
3 times, most recently
from
85b5556 to
2439b83
Compare
Signed-off-by: ntkathole <[email protected]>
ntkathole
force-pushed
the
codeflare_final
branch
from
2439b83 to
8a2cfab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR adds comprehensive support for KubeRay clusters via CodeFlare SDK integration, enabling Feast to run Ray workloads on Kubernetes-managed Ray clusters. It also consolidates Ray initialization logic across local, remote, and KubeRay modes into a unified architecture.
ray_initializer.pyconsolidates all Ray initialization logic.Which issue(s) this PR fixes:
Fixes #5633