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

Ideally the volumes would not _live_ on the nodes; they would be separate, but mounted to the nodes

For example, someone using AWS storageclasses with a statefulset would not need to care about the nodes, other than that enough of them exist to be able to schedule the pods

thanks for sharing your thoughts.

in my case, the statefulset apps are deployed on a k8s cluster on bare metal, and it's latency sensitive, which means i can only use `storageclass` like `localssd` (not remote storage)

i see. sounds like the immutable worker node pattern is not a good fit for your situation unless you can find a way to decouple the data from the nodes while maintaining acceptable latency