improve: more strict delete condition (#2722)

Author: csviri

Diff for: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/workflow/KubernetesResourceDeletedCondition.java

@@ -4,13 +4,9 @@
 import io.javaoperatorsdk.operator.api.reconciler.Context;
 import io.javaoperatorsdk.operator.api.reconciler.dependent.DependentResource;
 
-/**
- * A condition implementation meant to be used as a delete post-condition on Kubernetes dependent
+/* A condition implementation meant to be used as a delete post-condition on Kubernetes dependent
  * resources to prevent the workflow from proceeding until the associated resource is actually
- * deleted from the server (or, at least, doesn't have any finalizers anymore). This is needed in
- * cases where a cleaning process depends on resources being actually removed from the server
- * because, by default, workflows simply request the deletion but do NOT wait for the resources to
- * be actually deleted.
+ * deleted from the server.
  */
 public class KubernetesResourceDeletedCondition implements Condition<HasMetadata, HasMetadata> {
 
@@ -20,10 +16,6 @@ public boolean isMet(
       HasMetadata primary,
       Context<HasMetadata> context) {
     var optionalResource = dependentResource.getSecondaryResource(primary, context);
-    if (optionalResource.isEmpty()) {
-      return true;
-    } else {
-      return optionalResource.orElseThrow().getMetadata().getFinalizers().isEmpty();
-    }
+    return optionalResource.isEmpty();
   }
 }