I am investigating a method of running database migrations (Ruby on Rails, Django, etc) in Helm in a Job with “helm.sh/hook”: pre-install,pre-upgrade . By all accounts, it should work fine. This seems like the best way to run database migrations via a helm deployment.
However, in a blog post someone mentioned that if the Job takes too long it might time out.
Would Helm’s global 5 minute timeout apply to pre-install jobs? That is, if a Job takes more than 5 minutes, for whatever reason, any reason, even if it’s constantly returning data to stdout/stderr, then Helm will consider that the Job has “timed out”? What are the criteria for a timeout to happen on a pre-install Job in Helm?