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

You can tell the Service to not wait on the resources

```"<http://pulumi.com/skipAwait|pulumi.com/skipAwait>": pulumi.String("true"),```

<https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/>

Beyond this, I don’t know, I asked a similar question to yours last year. :slightly_smiling_face:

does this actually skip the await?

I honestly, not sure if I want to _skip_ the await

because I _think_ I want to know if something is broken

but I do need to deploy multiple things at once, in order to make it work

What it does is basically mark the service as ready even though the underlying pods are not there yet.

In my system, I have the Service deployed first, and then a Deployment that references it (as a dependency) which is also going to create the pods that match the service

So if I waited on the Service being ready, then I’d have a deadlock (as you described). You just need to break the chain somewhere.

I still want to know whether or not the service is actually healthy

I’m comparing to ArgoCD right now, as you can define “waves”, and all resources within a wave and deployed at once, and you move onto the next wave when all resources are healthy

I need to deploy multiple things simultaneously, while still having the “await” health checking. I just don’t want that health checking to block applying of other resources with this “wave” (concept)

the health checking should still take place, and prevent the next “wave”

<https://github.com/pulumi/pulumi-kubernetes/issues/1875>

I think there maybe needs to be a bigger conversation about this?

Yeah, I’m not 100% sure if this is a use case that’s really solvable, as you have a cyclic dependency but you want the cycle to be ignored, but that doesn’t really work if you want to maintain the dependency chain.