You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
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.
The text was updated successfully, but these errors were encountered: