potiuk commented on PR #29624: URL: https://github.com/apache/airflow/pull/29624#issuecomment-1437306653
> I believe some of the `CeleryKubernetesExecutor` users use the same configuration for celery and k8s, if we separate the configurations in two sections, they will need to duplicate them. With my suggestion, they can keep them identical, or override them/some of them in the section k8s_pod_template Hmm. I think the whole reason to have CeleryK8S executor was to make them "different" - I think characteristics (memory, CPU etc. ) of "always running" celery worker Pod - which usually has N Python interpreter started (celery parallelism) is pretty much always different than K8S Pod (which always runs 1 task). I think it would be rather counter-productive to commonalize those settings -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
