During the initial creation of the migration job, the job's pod fails to start when k8s_migrations_enabled is set to true (which it is by default) because app-secrets have yet to be generated.
A workaround is to temporarily set k8s_migrations_enabled to false for the first deploy, and then re-enable for subsequent deploys.
During the initial creation of the migration job, the job's pod fails to start when
k8s_migrations_enabled
is set to true (which it is by default) becauseapp-secrets
have yet to be generated.A workaround is to temporarily set
k8s_migrations_enabled
to false for the first deploy, and then re-enable for subsequent deploys.