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

i'd start by eliminating those changes, are you sure the nodepool instance size changing isn't immutable?

is there an upgrade path for the version from 1.18.3 -&gt; 1.18.14? Reduce the amount of changes that are happening

I can make both changes through DO's UI.

Through the API I can update version

<https://developers.digitalocean.com/documentation/v2/#upgrade-a-kubernetes-cluster>

But the node pool requires a delete-replace.

It seems that this is a gap in capability for Pulumi DO's package. The planner doesn't know how to upgrade version nor does it treat node pool as its own resource which would be fine to delete-replace as long as replacement is created first, which pulumi would do by default

we bridge our pulumi provider from the terraform one, here's the upstream issue tracking it:

<https://github.com/digitalocean/terraform-provider-digitalocean/issues/182>

<https://github.com/digitalocean/terraform-provider-digitalocean/issues/424#issuecomment-650419545>

if you use this resource to build your node pool:

<https://www.pulumi.com/docs/reference/pkg/digitalocean/kubernetesnodepool/>

this won't happen

changing the default node pool on a cluster is immutable, changing an additional one is not