Is the recommended way of managing migrations with Kubernetes still

initContainers

? Would something like https://github.com/pulumi/pulumi-kubernetes/pull/633 help with waiting for a migration

Job

to finish before deploying other resources?

Yeah, I’ve seen it done both ways. The Job resource will wait until it has run to completion, so that can be a good option if you don’t want to use

initContainers

.

Great! Thanks 🙂

The API docs have more detailed info on the await behavior of each k8s resource: https://www.pulumi.com/docs/reference/pkg/kubernetes/batch/v1/job/