@white-balloon-205 I have a weird behaviour. I’m provisioning a gke cluster with pulumi, no issue here. But if I try to delete it (removing it from the stack), the update went well, everything is flagged as deleted and exit without error, yet the cluster is still there in gke. Is this a problem with the terraform provider under the hood, or is it a feature or intended (and if so should be explicitly mentioned) ?

This definitely sounds like a bug to me!

@stocky-spoon-28903 well, that’s on a private repo but I can definitely make a quick and short example if needed. In fact what you need to do is only create a new

gcp.container.Cluster

then try a

pulumi destroy

or even just commenting out the

Cluster

definition and run a

pulumi up

again.

Ok I’ll open an issue for this later this morning - the behaviour is not expected. Last question: what version of the provider, language package and CLI are you using?

"@pulumi/gcp": "^0.16.0",
"@pulumi/kubernetes": "^0.18.0",
"@pulumi/pulumi": "^0.16.8"

$ pulumi version
v0.16.8

Thanks.

OK great, thanks ! Let me know if you need more information or if I can help to test anything