[GitHub] [airflow] potiuk commented on pull request #29624: Can't configure Kubernetes and Celery workers in Helm Chart

potiuk commented on PR #29624: URL: https://github.com/apache/airflow/pull/29624#issuecomment-1445151205 I think... Let's try what @hussein-awala proposes :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

[GitHub] [airflow] potiuk commented on pull request #29624: Can't configure Kubernetes and Celery workers in Helm Chart

potiuk commented on PR #29624: URL: https://github.com/apache/airflow/pull/29624#issuecomment-1437309061 (BTW. @amoghrajesh - adding `Closes #PR` inside comment does not work :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [airflow] potiuk commented on pull request #29624: Can't configure Kubernetes and Celery workers in Helm Chart

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

[GitHub] [airflow] potiuk commented on pull request #29624: Can't configure Kubernetes and Celery workers in Helm Chart

potiuk commented on PR #29624: URL: https://github.com/apache/airflow/pull/29624#issuecomment-1437263567 I think the idea in the #28800 was to be able to specify some parameters in the Helm Chart Values in a similar way for K8S as it si for celery. What it would likely mean - is merging the