FloChehab opened a new issue #11979: URL: https://github.com/apache/airflow/issues/11979
Hello, We are used to using `helm install` / `helm upgrade` with the `--wait` option ; which is nice because the command returns only if install / upgrade is kind of done and not just "commited". Unfortunately it doesn't currently play really nice with the chart as: * The migrate database job is set to run "post-install" & "post-upgrade" (https://github.com/apache/airflow/blob/master/chart/templates/migrate-database-job.yaml#L35) * The init containers actually wait for the migrations to be applied on install. So if the database hasn't been migrated yet, the install / upgrade fails waiting for the migrations to be applied with the `--wait` option. One option would be to switch to run the migrations with `pre-install` and `pre-upgrade` hooks instead. I'd enable this behavior only if we have an external database (in a more production friendly env. where we are more likely to use the `--wait` option too -?-). If we use a database deployed by the chart, I don't think this could play nice. What do you think ? PS: another small question related to this ; on airflow versions bump (with schema migrations to perform), are we expecting the RollingUpdate of pods to work (ie are the schemas backward compatible for one airflow version bump). -- 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. For queries about this service, please contact Infrastructure at: [email protected]
