[GitHub] [airflow] potiuk commented on issue #20168: KubernetesExecutor reports missing dag_run.data_interval_start on airflow@2.2.1

[GitBox <gi...@apache.org>]

potiuk commented on issue #20168:
URL: https://github.com/apache/airflow/issues/20168#issuecomment-989924490


   Yeah. You have to keep your pod template and base image synced after the update. 
   
   I think this will be handled much better soon with #18439 - when DB migrations will be involved and not applied, your K8S job should fail with an appropriate message. But I think this also comes back to our earlier discussion @kaxil  @jedcunningham  @dimberman  (with migration containers) -  what happens if there are two different Airlow versions In KE and airflow when there is no "migration" between them?
   
   Should we flag that as an error? Should we check if the airflow version is right in the image? I think that would make sense to pass Airflow version when KE submits the job and we should at least check if the versions match, because there might be cses like this one that will be very difficult to debug otherwise.
   
   WDYT?


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org