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

These seems like general EKS questions rather than pulumi questions..

however, questions:
• do you have a pod disruption budget set on your stateful workloads?
• have you tried an operator like: <https://github.com/TwiN/aws-eks-asg-rolling-update-handler> ?
• have you tried setting the max unavailable settings in the update config? <https://www.pulumi.com/registry/packages/aws/api-docs/eks/nodegroup/#nodegroupupdateconfig>

I guess it is more of an EKS question than Pulumi. Is there an EKS slack out there? I guess I should go and find out.

I do have pod disruption budgets set but updating the node pool seems to ignore them

I have not tried that operator I will go have a gander, thanks.

I haven't explicitly set the max unavailable, but I don't think that would help, the node pool always has enough available nodes it's just the pvc can't be satisfied as the ebs vol is attached to a dying node, and won't be free for 8 mins.