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
// An update of an existing object will be performed if it is considered to be out of sync; that means:
224
233
// - the object's manifest has changed, and the effective reconcile policy is ReconcilePolicyOnObjectChange or ReconcilePolicyOnObjectOrComponentChange or
225
234
// - the specified component has changed and the effective reconcile policy is ReconcilePolicyOnObjectOrComponentChange or
226
-
// - periodically after forceReapplyPeriod.
235
+
// - periodically after the specified force-reapply interval.
227
236
//
228
237
// The update itself will be done as follows:
229
238
// - if the effective update policy is UpdatePolicyReplace, a http PUT request will be sent to the Kubernetes API
Copy file name to clipboardExpand all lines: website/content/en/docs/concepts/dependents.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,7 @@ To support such cases, the `Generator` implementation can set the following anno
44
44
-`mycomponent-operator.mydomain.io/apply-order`: the wave in which this object will be reconciled; dependents will be reconciled wave by wave; that is, objects of the same wave will be deployed in a canonical order, and the reconciler will only proceed to the next wave if all objects of previous waves are ready; specified orders can be negative or positive numbers between -32768 and 32767, objects with no explicit order set are treated as if they would specify order 0
45
45
-`mycomponent-operator.mydomain.io/purge-order` (optional): the wave by which this object will be purged; here, purged means that, while applying the dependents, the object will be deleted from the cluster at the end of the specified wave; the according record in `status.Inventory` will be set to phase `Completed`; setting purge orders is useful to spawn ad-hoc objects during the reconcilation, which are not permanently needed; so it's comparable to Helm hooks, in a certain sense
46
46
-`mycomponent-operator.mydomain.io/delete-order` (optional): the wave by which this object will be deleted; that is, if the dependent is no longer part of the component, or if the whole component is being deleted; dependents will be deleted wave by wave; that is, objects of the same wave will be deleted in a canonical order, and the reconciler will only proceed to the next wave if all objects of previous saves are gone; specified orders can be negative or positive numbers between -32768 and 32767, objects with no explicit order set are treated as if they would specify order 0; note that the delete order is completely independent of the apply order
47
+
-`mycomponent-operator.mydomain.io/reapply-interval` (optional): the interval after which a force-reapply of the object will be performed (even it is in sync otherwise); if not specified, the reconciler default is used; note that, even if the specified force-reapply interval has passed, the next reconcile may happen only after the current requeue interval is over; because of that, it makes sense to set the reapply interval to a value (significantly) larger than the effective requeue interval.
47
48
-`mycomponent-operator.mydomain.io/status-hint` (optional): a comma-separated list of hints that may help the framework to properly identify the state of the annotated dependent object; currently, the following hints are possible:
48
49
-`has-observed-generation`: tells the framework that the dependent object has a `status.observedGeneration` field, even if it is not (yet) set by the responsible controller (some controllers are known to set the observed generation lazily, with the consequence that there is a period right after creation of the dependent object, where the field is missing in the dependent's status)
49
50
-`has-ready-condition`: tells the framework to count with a ready condition; if it is absent, the condition status will be considered as `Unknown`
0 commit comments