-
Notifications
You must be signed in to change notification settings - Fork 36
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
KubernetesPodOperator is not supported currently -> needs kubeconfig #14
Comments
I think one can always use mounted GCP credentials to retrieve GKE cluster kubeconfig by invoking gcloud: I'm not sure whether we want to expose any additional credentials stored locally to the running Composer Local Environment, let me get back to you on this. |
Thanks for you reply, Looking forward to your verdict. |
@piotrwrotniak it would be nice to either provide support to add custom docker volume mounts or support the airflow to K8s auth order as-is without the need for additional setup, the same way ADC works for gcloud auth without any intervention within the container. |
@piotrwrotniak What if you use a local cluster through minikube, Docker Desktop, etc? Aren't we talking about local development? This is a legit issue. |
Hi @piotrwrotniak, any update or estimation when issues/PRs in this repository are getting some attention? Otherwise forking will start very early, and it would be nicer if the OSS community is focused on one repository than in forks (esp. since the whole airflow/composer is relying on OSS) |
The way forward we'll be supporting custom mounts - we'll be working on this (Cloud Composer). |
@michalmodras do you know when you can expect an update? |
See #15 (comment), it will be included in the next release |
As per current setup, the local credentials are not mounted and have to be somehow manually copied. The file
~/.kube/config
is not mounted and hence inside the container you cannot interact with K8S clusters. Solution is needed to make K8s workloads testable in Airflow.Opened PR #15 please feel free to check
The text was updated successfully, but these errors were encountered: