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: content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,6 @@ content_type: concept
9
9
weight: 10
10
10
-->
11
11
12
-
13
12
<!-- overview -->
14
13
15
14
<!--
@@ -87,7 +86,7 @@ For specific information about how to install and manage a CNI plugin, see the d
87
86
For plugin developers and users who regularly build or deploy Kubernetes, the plugin may also need specific configuration to support kube-proxy.
88
87
The iptables proxy depends on iptables, and the plugin may need to ensure that container traffic is made available to iptables.
89
88
For example, if the plugin connects containers to a Linux bridge, the plugin must set the `net/bridge/bridge-nf-call-iptables` sysctl to `1` to ensure that the iptables proxy functions correctly.
90
-
If the plugin does not use a Linux bridge (but instead something like Open vSwitch or some other mechanism) it should ensure container traffic is appropriately routed for the proxy.
89
+
If the plugin does not use a Linux bridge, but uses something like Open vSwitch or some other mechanism instead, it should ensure container traffic is appropriately routed for the proxy.
91
90
-->
92
91
## 网络插件要求 {#network-plugin-requirements}
93
92
@@ -96,7 +95,7 @@ If the plugin does not use a Linux bridge (but instead something like Open vSwit
0 commit comments