https://pulumi.com logo
Title
b

bored-table-20691

05/20/2021, 7:55 PM
Is there a way when creating a service to tell it to not wait for any pods to be ready? Specifically, we create our services prior to creating the Deployments/DaemonSets, as we depend on the service environment variable injection to happen into the later-created pods. With Pulumi, I’ve expressed the dependency (i.e. the Deployment has a DependsOn the Service objects), but the Service itself never becomes ready as it is in stuck in the “Finding Pods to direct traffic to” stage (1/3). I’d like to tell it to not do that.
As I was writing this, I thought of a new place to look in the docs and found this:
'<http://pulumi.com/skipAwait|pulumi.com/skipAwait>: "true"'
. Let me try it.
b

billowy-army-68599

05/20/2021, 7:57 PM
ah you found it 🙂
b

bumpy-summer-9075

05/20/2021, 7:57 PM
well I'm glad you posted this, I learned something today 🙂
s

sparse-park-68967

05/20/2021, 8:02 PM
We are also working on a more global setting to skip the await logic: https://github.com/pulumi/pulumi-kubernetes/issues/1421
b

bored-table-20691

05/20/2021, 8:04 PM
Thanks @sparse-park-68967 and @billowy-army-68599, that did seem to work as I wanted it to. It would be nice if this was also a resource option and not just an annotation on the Kubernetes object itself.