Multiple Kustomizations managing the same resource #5611
Description
Currently, you can have multiple kustomizations managing the same kubernetes resource, for instance by having multiple kustomizations looking at the same path in a repo or a naming conflict.
This is typically because of a misconfiguration.
Since the value of the label kustomize.toolkit.fluxcd.io/name changes, the kustomize controller should know that this resource used to be managed by a different kustomization.
I propose that this should result in an error being thrown.
To remain compatible or if there are use cases where this is legitimate, maybe there should be an option in kustomization that its resources cannot belong to any other kustomization.
What do you think?