No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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`.

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/>