Move images to images folder

Signed-off-by: lou-lan <[email protected]>
spidernet-io · May 8, 2024 · 1089095 · 1089095 · weizhoublue · May 8, 2024
1 parent 12d0d85
commit 1089095
Show file tree

Hide file tree

Showing 15 changed files with 8 additions and 17 deletions.
diff --git a/docs/README.en.md b/docs/README.en.md
@@ -8,7 +8,7 @@ To solve this problem, EgressGateway has been introduced into the k8s cluster. I
 
 ## Architecture
 
-![Architecture](./architecture02.png)
+![Architecture](./images/architecture02.png)
 
 ## Why EgressGateway
 

diff --git a/docs/README.zh.md b/docs/README.zh.md
@@ -5,7 +5,7 @@
 
 ## 架构
 
-![Architecture](./architecture02.png)
+![Architecture](./images/architecture02.png)
 
 ## 为什么选择 EgressGateway
 

diff --git a/docs/backends.md b/docs/backends.md
diff --git a/...1-egress-gateway/Agent-Reconcile-Flow.png → docs/images/Agent-Reconcile-Flow.png b/...1-egress-gateway/Agent-Reconcile-Flow.png → docs/images/Agent-Reconcile-Flow.png
diff --git a/...ess-gateway/Controller-Reconcile-Flow.png → docs/images/Controller-Reconcile-Flow.png b/...ess-gateway/Controller-Reconcile-Flow.png → docs/images/Controller-Reconcile-Flow.png
diff --git a/...gress-gateway/Egress-Gateway-Datapath.png → docs/images/Egress-Gateway-Datapath.png b/...gress-gateway/Egress-Gateway-Datapath.png → docs/images/Egress-Gateway-Datapath.png
diff --git a/docs/Egress-Gateway.png → docs/images/Egress-Gateway.png b/docs/Egress-Gateway.png → docs/images/Egress-Gateway.png
diff --git a/docs/architecture.png → docs/images/architecture.png b/docs/architecture.png → docs/images/architecture.png
diff --git a/docs/architecture02.png → docs/images/architecture02.png b/docs/architecture02.png → docs/images/architecture02.png
diff --git a/docs/speed.svg → docs/images/speed.svg b/docs/speed.svg → docs/images/speed.svg
diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml
@@ -89,6 +89,7 @@ nav:
       - Failover: usage/EgressGatewayFailover.md
       - Move EgressIP: usage/MoveIP.md
       - Run EgressGateway on Aliyun Cloud: usage/Aliyun.md
+      - Troubleshooting: usage/Troubleshooting.md
   - Concepts:
       - Architecture: concepts/Architecture.md
       - Datapath: concepts/Datapath.md
@@ -102,7 +103,6 @@ nav:
       - CRD EgressClusterInfo: reference/EgressClusterInfo.md
       - egctl cli: reference/egctl.md
       - metrics: reference/metrics.md
-  - Troubleshooting: Troubleshooting.md
   - Development:
       - DataFlow: develop/Dataflow.md
       - Contribute: develop/Contribute.md

diff --git a/docs/proposal/01-egress-gateway/Egress-Gateway.png b/docs/proposal/01-egress-gateway/Egress-Gateway.png
diff --git a/docs/proposal/01-egress-gateway/EgressGateway.md b/docs/proposal/01-egress-gateway/EgressGateway.md
@@ -90,7 +90,7 @@ spec:
 
 ### Datapath
 
-<img src="Egress-Gateway-Datapath.png" width="70%"></img>
+<img src="../../images/Egress-Gateway-Datapath.png" width="70%"></img>
 
 A combination of vxlan tunnel, ipset, iptables, route is required to complete policy control.
 
@@ -162,12 +162,12 @@ iptables -t nat -I POSTROUTING 1 -m mark --mark 0x12000000 -j ACCEPT -m comment
 
 Controller consists of Webhook Validator and Reconcile Flow.
 
-<img src="Controller-Reconcile-Flow.png" width="70%"></img>
+<img src="../../images/Controller-Reconcile-Flow.png" width="70%"></img>
 
 Controller has 2 control processes, the first Watch cluster nodes, generate tunnel IP address and MAC address for Node, then `Create` or `Update` EgressTunnel CR Status. The second control flow watch `EgressTunnel` and `Egressgateway`, sync match node list from `labelSelector`, election egress gateway node.
 
 ### Agent
 
-<img src="Agent-Reconcile-Flow.png" width="70%"></img>
+<img src="../../images/Agent-Reconcile-Flow.png" width="70%"></img>
 
 Agent has two control processes, the first Watch `EgressTunnel` CR, which manages node tunnel, and node tunnel is a pluggable interface that can be replaced by Geneve. The second control process manages datapath policy, which watches `EgressTunnel`, `EgressGateway` and `Egresspolicy`, and sends them to the host through the police interface. It is currently implemented by a combination of *ipset*, *iptables*, and *route*, and it can be replaced by *eBPF*.
diff --git a/docs/Troubleshooting.en.md → docs/usage/Troubleshooting.en.md b/docs/Troubleshooting.en.md → docs/usage/Troubleshooting.en.md
@@ -24,7 +24,7 @@ The following are the data from our stress tests using bare metal servers.
 | case2 | egress vxlan -> egress vxlan | `9.11 Gbits/sec sender - 9.09 Gbits/sec receiver` |
 | case3 | pod -> egress node -> target | `9.01 Gbits/sec sender - 8.98 Gbits/sec receiver` |
 
-![egress-check](./speed.svg)
+![egress-check](../images/speed.svg)
 
 #### Virtual machine
 

diff --git a/docs/Troubleshooting.zh.md → docs/usage/Troubleshooting.zh.md b/docs/Troubleshooting.zh.md → docs/usage/Troubleshooting.zh.md
@@ -24,7 +24,7 @@ EgressGateway 使用了 vxlan 隧道，经过测试 vxlan 损耗在 10% 左右
 | case2 | egress vxlan -> egress vxlan | `9.11 Gbits/sec sender - 9.09 Gbits/sec receiver` |
 | case3 | pod -> egress node -> target | `9.01 Gbits/sec sender - 8.98 Gbits/sec receiver` |
 
-![egress-check](./speed.svg)
+![egress-check](../images/speed.svg)
 
 #### 虚拟机