GitHub user potiuk added a comment to the discussion: Add a "`DockerExecutor`" inside `CeleryExecutor`
Why not K8S executor? You generally want to reproduce pretty much everything K8S executor does, so it seems the easiest way for you will be to have K8S cluster and let Airflow use it to execute tasks via K8S Executor. Why do you want someone to basiclly reproduce what K8S does - i.e. run Pods scheduled in separate containers. If you want to implement any flexibility in such an executor, you will soon start reimplementing K8S. Why? Why not K8S (and the answer - because we do not want to use K8s is not good - essentially your feature request is to re-implement a lot of what it is). GitHub link: https://github.com/apache/airflow/discussions/58687#discussioncomment-15078763 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
