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

Does pulumi/gke drain the nodes when doing a replacement on the node pool in a way that a PDB would apply? Because when pulumi goes to replace a pool, my pods go down even though I have PDBs.

What I think I discovered is that this is on Google. Since Pulumi uses the Google API to delete the node pool, what Google does is to cordon off every node in the pool, and then start to delete each of them. I believe this ignores the PDBs.

It would be great if there was a way in pulumi to have it handle it via a rolling delete. Especially given that due to being pulumi, you can’t have 2 resources with the same name. So you can’t have a new node pools ready ahead of time.

<@UDEJ1F5SQ> Please let me know if we need to open a ticket for this or if something like this already has one if you can. Thanks!

<@UGDSK5RNC> I'm not aware of an issue (and my quick search didn't find one). Could you open one?

<https://github.com/pulumi/pulumi-gcp/issues/255>