You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/en/docs/documentation/reconciler.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ The framework out of the box supports this logic, it will always
37
37
call the `reconcile` method unless the custom resource is
38
38
[marked from deletion](https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/#how-finalizers-work).
39
39
40
-
On the other, if the resource is marked from deletion and if the `Reconciler` implements the
40
+
On the other hand, if the resource is marked from deletion and if the `Reconciler` implements the
41
41
[`Cleaner`](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/Cleaner.java) interface, only the `cleanup` method is called. By implementing this interface
42
42
the framework will automatically handle (add/remove) the finalizers for you.
0 commit comments