1fanwang commented on issue #70953: URL: https://github.com/apache/airflow/issues/70953#issuecomment-5186688690
Verified [Validate KubernetesResourceBaseOperator yaml_conf after rendering](https://github.com/apache/airflow/pull/70337) on `cncf-kubernetes 10.21.0rc1`. Works as intended. Airflow 3.3.0, two identical virtualenvs: one with the RC providers, one with the previous stable release. Same Dag, same command, run through the real task runner. Only the external transport is stubbed, and the stub asserts the value that actually reaches it. A `KubernetesCreateResourceOperator` with neither `yaml_conf` nor `yaml_conf_file`. Both versions fail, which is correct. The difference is whether the message tells you why. ```bash # cncf-kubernetes 10.21.0rc1 AIRFLOW_HOME=$PWD/airflow_home \ AIRFLOW__CORE__DAGS_FOLDER=$PWD/dags_e2e/rc_70337_k8s_resource \ .venv/bin/airflow dags test rc_70337_k8s_resource # cncf-kubernetes 10.20.0, identical Dag AIRFLOW_HOME=$PWD/airflow_home_prev \ AIRFLOW__CORE__DAGS_FOLDER=$PWD/dags_e2e/rc_70337_k8s_resource \ .venv-prev/bin/airflow dags test rc_70337_k8s_resource ``` ``` # cncf-kubernetes 10.21.0rc1 AirflowException: One of `yaml_conf` or `yaml_conf_file` arguments must be provided # cncf-kubernetes 10.20.0 AirflowException: ('File %s not found', None) ``` -- 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]
