-
Notifications
You must be signed in to change notification settings - Fork 403
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] Expose generated ray start
command for worker and head nodes.
#1560
Comments
@kevingreer Thanks for putting this together! We are now in the final stage of releasing v1.0. Will get back on this once v1.0 is released! |
Any progress on this? It seems the command is prepended to the
We'd like to apply it to before the |
I will work on this issue this week. |
@findmyway Do you mean |
For my case, I mean More details about my usage. I'm using micromamba in a custom docker image. It has an |
Search before asking
Description
KubeRay generates a
ray start
command to that is executed to start the cluster head node and cluster worker nodes. In aRayService
Kubernetes config when specifying the head and worker pod templates, you can add acommand
field, and that command will be prepended to the generatedray start
command, like$CUSTOM_CMD && $GENERATED_CMD
. The code for this functionality is here.This issue requests a feature that allows
$GENERATED_CMD
to be exposed to the custom command specified in the k8s config. After this feature is implemented, a person would be able to use the KubeRay generatedray start
command within their custom command specified in their pod templates.Use case
I have a binary that wraps arbitrary shell commands. This binary provides some general functionality useful for all services at my company, such as piping logs to our various logging systems. It is run like so:
./wrapper-binary --command "$CMD"
where
$CMD
can be any arbitrary command. For the use case of this issue, I would like$CMD
to beray start
command generated by KubeRay.Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: