diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-01-25 11:44:35 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-25 11:44:35 -0800 |
| commit | 509a04d573dcaed714ff14c865fe115bf9524993 (patch) | |
| tree | 86c68e43290e09a23503f5923e3bfb403a6a9e55 | |
| parent | 18e58e903c07ae8bf1a447ffb87c920b5ac87978 (diff) | |
| parent | cba82bfddff11939d4d4cffb4bf357c8008a88fc (diff) | |
Merge pull request #1689 from jbowes/add-another-level-based-reference
Add another reference on level-based concepts to architecture.md
| -rw-r--r-- | contributors/design-proposals/architecture/architecture.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/architecture/architecture.md b/contributors/design-proposals/architecture/architecture.md index 8387c886..0dc4ec40 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 |