Automatically Delete Resource if Dependent Removed From Workflow

If a dependent is removed from a workflow, the previously created resource represented by that dependent needs to be cleaned up. This can happen before the actual workflow is executed.
This could be done automatically before a workflow is executed, although it is not trivial in general. There are two problems:

1. If a dependent is removed, on startup the informer related to its type might not be added anymore. So we would need to mark somewhere (maybe status or annotation?) the GVk-s of resources managed.

2. If there are multiple resources of the same type in general it is not easy to identify which resource belongs to which dependent resource - without calling getSecondaryResource on the dependent. Since this cleanup would happen before the dependents are reconciled this is not doable without imposing additional requirements on implementation: for example, if the id of the resource is calculated based on the desired state, the desired state calculation might depend on other resources (which might not be reconciled now).
   Fortunately, this problem can be solved simply just by adding the name of the dependent as an annotation to the resource so it can be identified easily.

Commencez par examiner l’exécution du workflow ainsi que le cycle de vie de l’informer et des ressources dépendantes décrits dans l’issue. Déterminez comment conserver les kinds des ressources gérées et les noms des ressources dépendantes, puis définissez l’achèvement de sorte que le nettoyage ait lieu avant l’exécution pour les ressources dépendantes supprimées, sans confondre plusieurs ressources du même type.