Change parent of resource will lead to AlreadyExists problem

[liubog2008]

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

Steps to reproduce

1. Deploy ns nnn.
2. Deploy configmap nnn/xxx without parent nnn.
3. Change configmap nnn/xxx parent to nnn.
4. Fail to deploy configmap because nnn/xxx already exists.

Expected:

Success to deploy configmap again in step 4.

Actual:

Have to recover manually.

[mikhailshilkov]

I moved the issue to pulumi/pulumi because I think it's not kubernetes-specific.

[leezen]

@liubog2008 When you re-parented the ConfigMap, did you specify its alias when doing so? (see https://www.pulumi.com/blog/cumundi-guest-post/#find-relationships-between-resources for an example of doing this).

[liubog2008]

No, I just add a parent.

[leezen]

You'll need to alias to the original parent; else, the engine will attempt to create a new resource. Does this issue reproduce if you do that?

[liubog2008]

It resolve my problem but is not elegant. We know kubernetes has a declarative API, but pulumi lets me back to write the imperative logic.

In this case, I have to save some codes(alias) which may only be executed once.

[leezen]

Thanks for confirming. Once the resource is migrated, you can remove the alias. For context, #458 has a lot of discussion on the design. Open to taking any feature requests on how you think this could be easier.