[apisix-ingress-controller] branch master updated: docs: adapt design diagrams (#214)

[kvn]

This is an automated email from the ASF dual-hosted git repository.

kvn pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git


The following commit(s) were added to refs/heads/master by this push:
     new 0d4288a  docs: adapt design diagrams (#214)
0d4288a is described below

commit 0d4288a6f3f3d38538ad7d261bcf10791a7d0b30
Author: scn7th <51355917+scn...@users.noreply.github.com>
AuthorDate: Sun Jan 31 21:30:18 2021 +0800

    docs: adapt design diagrams (#214)
    
    * adapt design diagrams
    
    * change modules design schema
    
    Co-authored-by: scn7th <scn7th@163/com>
---
 docs/design.md                 |   6 +++---
 docs/images/cascade-update.png | Bin 0 -> 7458 bytes
 docs/images/diff-rules.png     | Bin 0 -> 26749 bytes
 docs/images/modules.png        | Bin 0 -> 13292 bytes
 4 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/design.md b/docs/design.md
index b37f73d..79ba619 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -23,7 +23,7 @@ Apache APISIX ingress for Kubernetes.
 
 ## Modules
 
-![Architecture](./images/module-1.png)
+![Architecture](./images/modules.png)
 
 ### 1.Ingress-types
 
@@ -97,7 +97,7 @@ At present, we have defined multiple CRDs, and these CRDs are 
responsible for th
 
 So, in `apisix-ingress-controller`, a broadcast notification mechanism is 
designed through `channel`, that is, the definition of any object must be 
notified to other objects related to it and trigger the corresponding behavior.
 
-![hierarchical](./images/hierarchical.png)
+![hierarchical](./images/cascade-update.png)
 
 In a typical scenario, there is a many-to-many relationship between 
`ApisixRoute` and `ApisixService`, and a one-to-one relationship between 
`ApisixService` and `ApisixUpstream`.
 
@@ -114,7 +114,7 @@ The `seven` module internally saves memory data structures, 
which is currently v
 
 The current comparison rule is based on the grouping of `route` / `service` / 
`upstream` resource objects, compare them separately, and make corresponding 
broadcast notifications after finding the differences.
 
-![diff-flow](./images/diff-flow.png)
+![diff-flow](./images/diff-rules.png)
 
 ### Service Discovery
 
diff --git a/docs/images/cascade-update.png b/docs/images/cascade-update.png
new file mode 100644
index 0000000..cdc45eb
Binary files /dev/null and b/docs/images/cascade-update.png differ
diff --git a/docs/images/diff-rules.png b/docs/images/diff-rules.png
new file mode 100644
index 0000000..b1e3c88
Binary files /dev/null and b/docs/images/diff-rules.png differ
diff --git a/docs/images/modules.png b/docs/images/modules.png
new file mode 100644
index 0000000..3efc060
Binary files /dev/null and b/docs/images/modules.png differ