Maryam3107 commented on issue #46293:
URL: https://github.com/apache/airflow/issues/46293#issuecomment-2629394496
> ### Description
> Currently, when using executor_config with KubernetesExecutor, the
config_file path must be hardcoded. If we try to pass it dynamically using a
Jinja template ("{{ params.config_path }}"), it results in an error.
>
> Example of a working static configuration:
>
> executor_config={"KubernetesExecutor": {"config_file":
"/opt/airflow/config/kubernetes/docker-desktop-config.yaml"}}
> However, if we attempt to pass it dynamically, it fails:
>
> executor_config={"KubernetesExecutor": {"config_file": "{{
params.config_path }}"}}
> This would be useful when deploying DAGs across different environments
(e.g., multiple regions) without hardcoding paths.
>
> **Proposed Solution:**
>
> Modify executor_config to allow templating in
KubernetesExecutor.config_file, similar to other templated parameters in
Airflow.
>
> ### Use case/motivation
> This would be useful when deploying DAGs across different environments
(e.g., multiple regions) without hardcoding paths. Airflow should allow
config_file to accept templated values, resolving them at runtime. This feature
would improve flexibility when running KubernetesExecutor tasks that need
different configurations based on dynamic parameters. Would love to hear
thoughts from the community on this! Thanks! 😊
>
> ### Related issues
> This feature would improve Airflow’s flexibility in hybrid execution
environments and align with the goals of[
AIP-61](https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-61+Hybrid+Execution).
Would love to hear thoughts from the community on this! 🚀
>
> ### Are you willing to submit a PR?
> * [ ] Yes I am willing to submit a PR!
>
> ### Code of Conduct
> * [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
I can solve this problem. kindly assign it to me
--
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]
