Re: [I] Env_vars from KubernetesPodOperator does not assume secret (deploy as env var) because secrets are loaded after env vars into the pods. [airflow]

potiuk commented on issue #40092: URL: https://github.com/apache/airflow/issues/40092#issuecomment-2197011107 This is the way how env vars are passed - there is no way you can add secrets to env vars before - because they are evaluated in two different places. When you create k8s pod, you p

Re: [I] Env_vars from KubernetesPodOperator does not assume secret (deploy as env var) because secrets are loaded after env vars into the pods. [airflow]

ana-carolina-januario commented on issue #40092: URL: https://github.com/apache/airflow/issues/40092#issuecomment-2152675914 Hi, Additionally, I've tried multiple workarounds: 1. export to other env var like: export COMMAND_1=$COMMAND without success. 2. export the

[I] Env_vars from KubernetesPodOperator does not assume secret (deploy as env var) because secrets are loaded after env vars into the pods. [airflow]

ana-carolina-januario opened a new issue, #40092: URL: https://github.com/apache/airflow/issues/40092 ### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.6.0 ### What happened? We'