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: keps/sig-cloud-provider/5237-watch-based-route-controller-reconciliation/README.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -239,7 +239,6 @@ To ensure only a single reconciliation loop is run concurrently we use the [`k8s
239
239
240
240
Node updates are quite frequent. To reduce the number of requests sent to infrastructure providers, it’s important to filter these events and only trigger reconciliations when necessary.
241
241
242
-
TODO: more fields?
243
242
Two fields are relevant for determining whether a reconcile should occur:
244
243
245
244
1.`Node.Status.Addresses` maps to the `TargetNodeAddresses` field in the `Route` struct. It determines where packets for a give IP range should be sent. Changes to this field must trigger a reconcile.
0 commit comments