karenbraganz commented on issue #46714: URL: https://github.com/apache/airflow/issues/46714#issuecomment-2738333414
Another more straightforward option is to override pod resources with a [pod policy](https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/cluster-policies.html#airflow.policies.pod_mutation_hook) instead of a task policy like in [this example](https://www.astronomer.io/docs/learn/airflow-cluster-policies/#example-3). I was only able to use a task policy for my use case because I only wanted to override `executor_config` if it wasn't already set at the task level. If you want to set specific resources for all pods, you could try the pod policy. Still, in my opinion, it would be useful to add a setter to `executor_config` so it can be overridden for specific tasks using task policies. -- 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]
