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

Eliminate dependency on Camel-K CLI in operator mode #8

Open
tardieu opened this issue Jun 22, 2021 · 1 comment
Open

Eliminate dependency on Camel-K CLI in operator mode #8

tardieu opened this issue Jun 22, 2021 · 1 comment

Comments

@tardieu
Copy link
Member

tardieu commented Jun 22, 2021

Rayvens currently uses the Camel-K CLI to deploy Camel integrations with the Camel-K operator. Therefore, even in operator mode, the Ray image has to be augmented with the CLI to run Rayvens program. If we were to deploy integrations by directly interfacing with Kubernetes using the kubernetes Python library (or kubectl) already included in the base Ray image, we could eliminate the need for including the Camel-K CLI in the Ray image in operator mode.

@tardieu tardieu changed the title Eliminate dependency on Camel-K CLI in operator mode Eliminate dependency on Camel-K CLI and custom Ray image in operator mode Jun 22, 2021
@tardieu tardieu changed the title Eliminate dependency on Camel-K CLI and custom Ray image in operator mode Eliminate dependency on Camel-K CLI in operator mode Jun 22, 2021
@tardieu
Copy link
Member Author

tardieu commented Jun 22, 2021

To be clear, we still need the Camel-K operator to be deployed to the Kubernetes cluster but this is typically done beforehand, independently from deploying and configuring the Ray cluster itself.

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

No branches or pull requests

1 participant