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

[BUG] Ray Plugin RuntimeEnv isn't propagating to RayJob CRD #5843

Open
2 tasks done
peterghaddad opened this issue Oct 11, 2024 · 0 comments
Open
2 tasks done

[BUG] Ray Plugin RuntimeEnv isn't propagating to RayJob CRD #5843

peterghaddad opened this issue Oct 11, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@peterghaddad
Copy link
Contributor

peterghaddad commented Oct 11, 2024

Describe the bug

When specifying the runtime_env for a task, the runtimeEnvYAML field is unset in the created Ray Job on K8s i.e the CRD.

The

Expected behavior

For the end-user to have the ability to pass the runtime_env as a dictionary as part of the RayJobConfig.

Additional context to reproduce

Follow the example in the official Flyte documentation located here.

Additionally, tried performing a json.dumps(runtime_env) and passing it. The code accepts this; however, it is not propagated down.

Screenshots

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@peterghaddad peterghaddad added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Oct 11, 2024
@eapolinario eapolinario removed the untriaged This issues has not yet been looked at by the Maintainers label Oct 17, 2024
@eapolinario eapolinario self-assigned this Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants