This message was deleted.

Could you open an issue in Pulumi-kubernetes and link to this? Someone might need to look a little deeper into this.

It's not kubernetes related, it's AWS/EC2/EBS

Ahh - got it. Took a quick look - haven’t tried it yet but I expect this is related to needing to use

deleteBeforeReplace: true

to ensure the old instance is deleted before the new one is created - else the volume will still be attached to the old instance.

That works perfectly fine for me. Thanks a lot!

Thanks Luke

Is it possible to enforce pulumi to stop ec2 instance before detaching the volume on userdata change(and instance recreation)? https://github.com/avolkov-dev/pulumi-mount-issue/blob/master/index.ts#L16 Because now (without

forceDetach

) we are getting Error waiting for Volume (vol-xxx) to detach from Instance: i-xxx error) I believe this is because we trying to detach volume on running instance and getting timeouted