-
Notifications
You must be signed in to change notification settings - Fork 286
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
[Feature] Kuberay RayJob MultiKueue adapter #3892
[Feature] Kuberay RayJob MultiKueue adapter #3892
Conversation
Skipping CI for Draft Pull Request. |
/ok-to-test |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
@@ -70,6 +70,7 @@ IMAGE_TAG ?= $(IMAGE_REPO):$(GIT_TAG) | |||
JOBSET_VERSION = $(shell $(GO_CMD) list -m -f "{{.Version}}" sigs.k8s.io/jobset) | |||
KUBEFLOW_VERSION = $(shell $(GO_CMD) list -m -f "{{.Version}}" github.com/kubeflow/training-operator) | |||
KUBEFLOW_MPI_VERSION = $(shell $(GO_CMD) list -m -f "{{.Version}}" github.com/kubeflow/mpi-operator) | |||
KUBERAY_VERSION = $(shell $(GO_CMD) list -m -f "{{.Version}}" github.com/ray-project/kuberay/ray-operator) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So far it's the version without managedBy.
We don't have a ray-operator image that supports managedBy, that would have to be a custom one...
latest -> 1.2.2, which is the last release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, hopefully 1.3 of KubeRay is released before 0.11 of Kueue and the actually released support will rely on managedBy. @andrewsykim do you know the the KubeRay release is planned?
export KUBERAY_MANIFEST="${ROOT_DIR}/dep-crds/ray-operator/default/" | ||
export KUBERAY_IMAGE=bitnami/kuberay-operator:${KUBERAY_VERSION/#v} | ||
export KUBERAY_RAY_IMAGE=rayproject/ray:2.9.0 | ||
export KUBERAY_RAY_IMAGE_ARM=rayproject/ray:2.9.0-aarch64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this one is for us people working on macOS, it's vital for development, not so much for prod - I think it should stay
pkg/controller/jobs/raycluster/raycluster_multikueue_adapter.go
Outdated
Show resolved
Hide resolved
pkg/controller/jobs/raycluster/raycluster_multikueue_adapter.go
Outdated
Show resolved
Hide resolved
d27f12c
to
ad4df0d
Compare
pkg/controller/jobs/raycluster/raycluster_multikueue_adapter.go
Outdated
Show resolved
Hide resolved
ad4df0d
to
b13ce9a
Compare
/retest |
d3974b4
to
3c3a0c7
Compare
Actually, could you maybe split the PR into smaller parts:
|
1801ddc
to
106712f
Compare
I guess it's no longer valid, as there is no fix, rather extension for MK |
/release-note-edit
We may revisit the release note when the support relies on managedBy. |
test/integration/controller/jobs/rayjob/rayjob_controller_test.go
Outdated
Show resolved
Hide resolved
@mszadkow do you know why |
It won't anymore, I have reverted one change to get logs for the fail - #3892 (comment) |
d46ed43
to
3cfcc59
Compare
3cfcc59
to
11791fb
Compare
11791fb
to
4d84973
Compare
9f36f9d
to
362733f
Compare
362733f
to
8f174bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
Thanks!
Please follow up with integration tests. For now I believe the e2e tests + unit tests are providing enough coverage to merge, but going forward I want to make sure integration tests are added, so that we can test some bugfixes or features without extending the heavy e2e tests.
LGTM label has been added. Git tree hash: e24a7a5c8fb7053c6d7dd5c6c84ccba7bcb3821c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mimowo, mszadkow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
We want to be able to run Kuberay workloads RayJob in MultiKueue.
RayCluster will come as separate PR.
Testing:
Unit and multikueue e2e tests are provided.
Multikueue integration tests will be provided in separate PR - agreed with @mimowo.
Which issue(s) this PR fixes:
Relates to #3822
Special notes for your reviewer:
Does this PR introduce a user-facing change?