From cba82bfddff11939d4d4cffb4bf357c8008a88fc Mon Sep 17 00:00:00 2001 From: James Bowes Date: Thu, 25 Jan 2018 14:33:20 -0400 Subject: [PATCH] Add another reference on level-based concepts to architecture.md --- contributors/design-proposals/architecture/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/architecture/architecture.md b/contributors/design-proposals/architecture/architecture.md index 8387c886f..0dc4ec40b 100644 --- a/contributors/design-proposals/architecture/architecture.md +++ b/contributors/design-proposals/architecture/architecture.md @@ -110,7 +110,7 @@ including default values, and observed state (status). Controllers work continuously to drive the actual state towards the desired state, while reporting back the currently observed state for users and for other controllers. -While the controllers are [level-based](http://gengnosis.blogspot.com/2007/01/level-triggered-and-edge-triggered.html) +While the controllers are level-based (as described [here](http://gengnosis.blogspot.com/2007/01/level-triggered-and-edge-triggered.html) and [here](https://hackernoon.com/level-triggering-and-reconciliation-in-kubernetes-1f17fe30333d)) to maximize fault tolerance, they typically `watch` for changes to relevant resources in order to minimize reaction latency and redundant work. This enables decentralized and decoupled