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

This is veery hacky but you could use the `Command` resource from `@pulumi/command` to run the `kubectl` CLI in a loop forever until the daemonset pods are ready, and set a customTimeout for the Command resource

Oh yeah I could even use something like `kubectl rollout status` to wait for the DaemonSet deploy to complete, right? I’ll have to check, but I don’t think I have a `kubectl` binary (or a corresponding config) to use in my deployment pipeline. Sounds like I’d have to at least get the `kubectl` binary. But maybe I could effectively get a `.kube/config` out of pulumi since it already has the necessary creds?

Ah, never mind. I found some existing code we have to grab the kubeconfig :smile:

Yeah you’ll need the binary unless you opt for making the API call through something like curl.