You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any managed resources that are composed into a composite will have their controller reference set to point to the composite. I don't think there's ever a situation where a managed resource with a controller reference is a valid target for a claim that sets an explicit resourceRef, so perhaps we could solve this by adding a check to the claim binding Bind() methods that refuses to bind to a managed resource with a non-nil controller reference.
negz
transferred this issue from crossplane/crossplane
May 7, 2020
What problem are you facing?
Claims bind to resources whose binding status is
Unbound
and composed resources never becomeBound
How could Crossplane help solve your problem?
Composed resources shouldn't be claimed by others.
The text was updated successfully, but these errors were encountered: