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

<@UD2HJDBCL> 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

Man 8 hours that's a long time for rollout

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

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

:smiling_face_with_smiling_eyes_and_hand_covering_mouth:

Currently over 400 EBS volumes attached to my k8s clusters lol

oh well, at least theres pulumi. Doing this with anything else would be a nightmare

you should give a talk about this somewhere

We should think about how we can make this experience better for you…

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.