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

Add In-cluster support for k8 #33

Open
venkatajagannath opened this issue Aug 5, 2024 · 3 comments
Open

Add In-cluster support for k8 #33

venkatajagannath opened this issue Aug 5, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@venkatajagannath
Copy link
Contributor

No description provided.

@pankajastro
Copy link
Collaborator

Hey @venkatajagannath, could you please provide a description and outline the limitations for this issue? Thanks!

@venkatajagannath
Copy link
Contributor Author

Not a limitation as such.

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.

@venkatajagannath venkatajagannath added the enhancement New feature or request label Aug 15, 2024
@VinSnowski
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants