https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
g
@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
b
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
g
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
c
We could accommodate this with annotations
But yes I agree
Man 8 hours that's a long time for rollout
b
awful stateful app that needs 240GB of ingest data before it starts serving requests 🤮
c
holy cow
b
yeah imagine 50 of them, all forked off the same shitty code
20 nodes per replica
c
🤭
oh my
b
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
c
@busy-umbrella-36067 this is incredible
you should give a talk about this somewhere
We should think about how we can make this experience better for you…
b
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.
3 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by