This message was deleted.

Hi John. I’ve always used release, as you say pulumi will try to delete the resources before provisioning the new ones (or simultaneously). If you can’t afford to have any down time whilst provisioning, I’d probably recommend provisioning a stack side by side and destroying the old one. Is that a possibility?

I'm willing to have downtime 🤔 The issue, when I've played around, is that it will delete the chart and install the helm resource simultaneously. Say I have StatefulSet

x

in the chart

simple

. The

pulumi apply

will spit out

resource simple/x was not successfully created by the Kubernetes API server : statefulsets.apps "x" already exists

. I need the delete to happen first. This is not implemented. I'm iffy about running

pulumi destroy --target

. That would solve the simultaneity problem. (I'm lucky that the resource isn't in a

dependsOn

block of another resource. I had a different issue once like this and when the resource is in a dependsOn block of another component, selectively deleting it is difficult).

I’d try destroying the stack as it is then running a fresh up

Yeah you need to do a two phase release, pulumi has no way to do "delete before upsert" dependencies between resources.

I was playing with the code. It is pretty easy to add a manual

isUpgrade

flag to the code. (I have that coded up.) Don't see a way to find out whether something actually is an upgrade (if the k8s.helm.v3.Chart resource is new or being updated). Any clues?