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
Users can still use the same k8 cluster for OSS Airflow and Ray. In the current implementation, they would have to provide the kubeconfig manually.
To enable a feature within the connector where a user can select 'InCluster=True', we need to pass the kubeconfig as a file to the bash command that installs the kuberay operator.
Hey, I have just stumbled upon this because I am running Airflow and Ray inside the same cluster. I was wondering if there is a reason that Ray Provider does not use the config.load_incluster_config() from kubernetes package to get the kubeconfig in the same way that the cnfc.kubernetes Provider in Airflow use? Is this simply something that is not implemented yet?
No description provided.
The text was updated successfully, but these errors were encountered: