Hello there Does anyone know of a workaround for

Question

Hello there Does anyone know of a workaround for Add await logic for DaemonSets My service is deployed as a DaemonSet and we ve been running into some stability issues in our deployment pipeline lately Currently we re alerting with kube state metrics to detect the problem but it d be way nicer if `pulumi up` failed when some or all pods from our DaemonSet could not become ready within some duration I ve been crawling through other issues to try and find solutions and found a few that are relevant Support user specified readiness await logic CustomResource lifecycle causes issues with importing created resources Support custom logic in resource lifecycle And through those I ve found a couple of promising pointers But I can t quite piece together how I d actually block `pulumi up` on the DaemonSet becoming ready and throw an error So far all I ve been able to do is get the DaemonSet status showing as a stack output but that s not too helpful on its own sweat smile

steep-toddler-94095 · Answer

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

melodic-knife-7189 · Answer

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

melodic-knife-7189 · Answer

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

steep-toddler-94095 · Answer

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

melodic-knife-7189 · Answer

Makes sense thank you