on the kubernetes provider, is pulumi able to wait until a

StatefulSet

or

Deployment

has the disired amount of pods? This is from an old workflow, runs after the k8s resources have been applied, makes sure that the containers start up successfully and pass their readiness Checks

kubectl rollout status statefulset <NAME>

@busy-umbrella-36067 Pulumi should track Pods for Deployment, but StatefulSet hasn't been implemented yet. I'm working on that right now, and progress is being tracked at https://github.com/pulumi/pulumi-kubernetes/issues/93

could that possibly be toggled on/off somehow? I do have some

StatefulSets

that take 8+ hours to pass health checks. Maybe even allow a custom timeout on individual resource creation

Could you open an issue with some more details on what you'd need? In general, I think the expectation is that a Deployment/StatefulSet wouldn't be "ready" until any defined readiness/liveness checks were healthy

We could accommodate this with annotations

awful stateful app that needs 240GB of ingest data before it starts serving requests 🤮

holy cow

yeah imagine 50 of them, all forked off the same shitty code

🤭

Currently over 400 EBS volumes attached to my k8s clusters lol

@busy-umbrella-36067 this is incredible

I might do something on making easy custom state machines (fed via YAML) with Pulumi. I can’t really share much specifics about the current work.