What I would not expect is for it to fail with a name already exists, then if you change the name it fails to understand the old cluster is still there and doesn't do a proper replace

Can you file an issue? That sounds like a bug

I think it’s the kind of things that needs the

deleteBeforeReplace: true

option. And I’m not sure whether doing it transparently for resources is a good idea or not. But yeah, it’d be great if there will be some notification about it during the preview

yes that does resolve it