explicit actions on bosh-delete deployment #30
Description
As of v39, the default mechanism to tentative clean the k8s cluster is unsufficient:
- induces deadlocks / frozen namespace when deleting crds
- some constructs are not deletable without a precise explicit order (eg: crd, cr)
- some constructs are just useless to delete (local scope)
- some constructs must be absolutly deleted (external resources, like dns, vip, ...). In that case, deletion failure should block bosh delete-deployment for further manuel operation.
To adress these issue, suggest adding a new action list, to trigger apply sequencially on bosh delete-deployment.
spec.on_delete_actions: []