I have a kubernetes cluster with a dozen of deployments and services. I've set dependencies (through inputs-outputs) such that 1. deployments depend on some services (those that the deployment connects to) 2. every service depends on it's matching deployment. 3. every deployment depends on a secret This way everything works, but create, update and destroy of the cluster is VEEEEERY SLOW NOw, if I lift the dependencies in (2) during create I see the following Many (but not all, why?) services appear (as per kubectl get services) and then everything is stuck forever for the secret is never created. The secret does not depend on anything. Why is it not created? I have an impression that pulumi simply has a limit on number of resources in "creating state". if this limit is reached pulumi won't create new resources even though they don't have any dependencies and even though those resources waiting for something will wait forever Does that make sense?

default parallel is set here https://github.com/pulumi/pulumi/blob/master/pkg/cmd/pulumi/up.go#L41-L43

I believe any program must be able to succeed even with parallel = 1, If I'm not mistaken parallel is a performance option, not a correctness option

I would make a GH issue, ideally with a small repro