What happened?

The resource claim reconciler supports either dynamically or statically provisioning managed resources. The former involves using a resource class to create a new managed resource, while the latter involves binding to an existing resource.

A resource claim is the Kubernetes owner reference of any managed resource it dynamically provisions, but not the owner reference of any statically provisioned managed resource it later binds to. When a resource claim is deleted its underlying managed resource will only be deleted if it was dynamically provisioned and the user did not supply the --cascade option to kubectl delete.

While it is possible to delete a resource claim without deleting its managed resource, the resource claim reconciler doesn't currently update the managed resource in this scenario. It remains in binding state "bound", with a claim reference to the (now deleted) claim that it was bound to. This is probably not the behaviour we want.

How can we reproduce it?

1. Statically provision a Crossplane managed resource
2. Create a claim that specifies the managed resource from step 1 in its .spec.resourceRef
3. Wait for the claim and resource to bind.
4. Delete the claim created in step 2
5. Observe that the managed resource created in step 1 continues to be "bound" to the now deleted resource claim.

What environment did it happen in?

Crossplane version: