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

Isn’t that doing exactly what replaceOnChange and deleteBeforeReplace has asked it to do? Honestly I never did understand why anyone would set those to true for stateful assets.

Best bet is to disable those settings so statefuls persist, then migrate state to newly created asset. For the stateless stuff, it should be easy to blow away and recreate anytime so long as your customers hit you through static domain names.

<@U05J4JC7J6L> thanks for the answers, you are right. My PVC was configured to not to be replaced unless the size is changed, but the flags were there for deployment. So I expected the PVC to persist and deployment to be replaced. I'm currently renovating a script that uses automation API, in the old version there were lots of classes extended from ComponentResource, each having type names. Say below is the new version:
```TYPE                                            NAME
companyname:productType:product                 instance-name
  kubernetes:core/v1:Namespace                  instance-name
  companyname:productType:product:disk          instance-name
    kubernetes:core/v1:PersistentVolumeClaim.   instance-name
  companyname:productType:product:deployment.   instance-name
    kubernetes:core/v1:Deployment               instance-name```
And new version is like:
```TYPE                                            NAME
companyname:product                             instance-name
  kubernetes:core/v1:Namespace                  instance-name
  kubernetes:core/v1:PersistentVolumeClaim.     instance-name
  kubernetes:core/v1:Deployment                 instance-name```
So what happens is Pulumi first creates the resources needed on new version (things mostly already exists on the cluster) and deletes the resources from old version, causing resources that already exist to get deleted.

Is there a way to rename the types and shuffle the tree by keeping at least PVC the same?