When a user deletes a KfDef resource, the associated resources created by the plugin, such as ConfigMaps, Secrets, and Routes, are not automatically cleaned up. This leads to resource accumulation and potential clutter in the cluster.

The cleanup process should be enhanced to ensure that when a KfDef resource is deleted, all associated resources created by the defined plugin are also automatically deleted. This can be achieved by implementing appropriate resource-tracking mechanisms and incorporating them into the deletion workflow of the KfDef controller. 

In the case of created resources, we should consider using ownerReference. There are however patches we apply on existing resources as well - this should be investigated how we could revert those on deletion (if at all). One caveat here is that this needs to be manually invoked from the code in the delete phase of the plugin coordinator.