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/documentation/faq.md
+28-2Lines changed: 28 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,36 @@ layout: docs
5
5
permalink: /docs/faq
6
6
---
7
7
8
-
## Q: How can I access events?
8
+
###Q: How can I access the events which triggered the Reconciliation?
9
9
In the v1.* version events were exposed to `Reconciler` (in v1 called `ResourceController`). This
10
10
included events (Create, Update) of the custom resource, but also events produced by Event Sources. After
11
11
long discussions also with developers of golang version (controller-runtime), we decided to remove access to
12
12
these events. We already advocated to not use events in the reconciliation logic, since events can be lost.
13
13
Instead reconcile all the resources on every execution of reconciliation. On first this might sound a little
14
-
opinionated, but there was a sound agreement between the developers that this is the way to go.
14
+
opinionated, but there was a sound agreement between the developers that this is the way to go.
15
+
16
+
### Q: Can I re-schedule a reconciliation, possibly with a specific delay?
17
+
Yes, this can be done using [`UpdateControl`](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/UpdateControl.java) and [`DeleteControl`](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/DeleteControl.java)
0 commit comments