important-leather-2879603/18/2019, 7:38 PM
for the remainder of a deployment? I’m expecting one job to be run per deployment, and I know I’ve run into unique job name problems, as well as cleanup problems in past attempts. Another concern is that the job (db migration) may end up taking some time in the future - thinking about bigger column or table migrations and timeouts. Any thoughts/strategies that are working well?
gorgeous-egg-1692703/18/2019, 7:55 PM
important-leather-2879603/18/2019, 8:07 PM
gorgeous-egg-1692703/18/2019, 8:17 PM
important-leather-2879603/18/2019, 8:19 PM
breezy-hamburger-6961903/18/2019, 8:24 PM
that examines the pod’s annotation to determine if the Job should actually run after its been created - this gives us a bit of a lever to 1) guarantee the job gets created in k8s at pulumi update time and 2) we have a means and a lever to pull via annotation to determine if the Job is allowed or blocked to run