Should migrate database job run after pods are deployed when using Airflow Helm Chart and Kubernetes?

[ahipp13]

Hey all! Need some help understanding the Airflow Helm Chart.

The helm chart has a job called "migrate-database-job". When I read this, I would think that this would migrate the database for you before you deploy your other pods (scheduler webserver etc.)

But in the chart it has hooks "post-install, post-upgrade", which is why I am thinking it is spinning up before the job.

My question is, could somebody explain to me why this is set up like this? I also noticed that there are "wait-for-migrations" containers under my airflow pods as well.

Are you supposed to migrate the database BEFORE your new pods spin up with the new version, or is it okay to do it after with the "migrate-database-job"? If somebody could explain this all to me that would be greatly appreciated. Thank you!