Skip to content

Commit

Permalink
Merge pull request #2895 from ty-dc/docs/readme
Browse files Browse the repository at this point in the history
docs: typo
  • Loading branch information
weizhoublue authored Dec 14, 2023
2 parents b9e6d82 + 1735e9b commit b5c2a75
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 10 deletions.
2 changes: 1 addition & 1 deletion README-zh_CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ underlay CNI 主要指 macvlan、ipvlan、SR-IOV 等能够直接访问宿主机

* 增强的网络连通性

总所周知,原生的 macvlan ipvlan SR-IOV 存在诸多通信限制。但是,Spiderpool 打通 Pod 和宿主机的连通性,确保 Pod 健康检测工作正常,并可通过 kube-proxy 或 eBPF kube-proxy replacement 使得 Pod 访问 service,支持 Pod 的 IP 冲突检测、网关可达性检测等。多集群网络可基于相同的 underlay 网络或者 [Submariner](https://github.com/submariner-io/submariner) 实现联通。
众所周知,原生的 macvlan ipvlan SR-IOV 存在诸多通信限制。但是,Spiderpool 打通 Pod 和宿主机的连通性,确保 Pod 健康检测工作正常,并可通过 kube-proxy 或 eBPF kube-proxy replacement 使得 Pod 访问 service,支持 Pod 的 IP 冲突检测、网关可达性检测等。多集群网络可基于相同的 underlay 网络或者 [Submariner](https://github.com/submariner-io/submariner) 实现联通。

* eBPF 增强

Expand Down
2 changes: 1 addition & 1 deletion docs/README-zh_CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ underlay CNI 主要指 macvlan、ipvlan、SR-IOV 等能够直接访问宿主机

* 增强网络连通性

总所周知,原生的 macvlan ipvlan SR-IOV 存在诸多通信限制。但是,Spiderpool 打通 Pod 和宿主机的连通性,确保 Pod 健康检测工作正常,并可通过 kube-proxy 或 eBPF kube-proxy replacement 使得 Pod 访问 service,支持 Pod 的 IP 冲突检测、网关可达性检测等。多集群网络可基于相同的 underlay 网络或者 [Submariner](https://github.com/submariner-io/submariner) 实现联通。
众所周知,原生的 macvlan ipvlan SR-IOV 存在诸多通信限制。但是,Spiderpool 打通 Pod 和宿主机的连通性,确保 Pod 健康检测工作正常,并可通过 kube-proxy 或 eBPF kube-proxy replacement 使得 Pod 访问 service,支持 Pod 的 IP 冲突检测、网关可达性检测等。多集群网络可基于相同的 underlay 网络或者 [Submariner](https://github.com/submariner-io/submariner) 实现联通。

* eBPF 增强

Expand Down
16 changes: 8 additions & 8 deletions docs/reference/plugin-ifacer.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,14 +17,14 @@ This plugin dynamically creates VLAN sub-interfaces or Bond interfaces on the no
3. Configuring the address of VLAN/Bond interfaces during creation is not supported.
4. If your OS(such as Fedora, CentOS, etc.) uses NetworkManager, Highly recommend configuring following configuration file at `/etc/NetworkManager/conf.d/spidernet.conf` to prevent interference from NetworkManager with Vlan and Bond interfaces created by `Ifacer`:

```shell
~# INTERFACE=<your_interface_name>
~# cat << EOF | > /etc/NetworkManager/conf.d/spidernet.conf
> [keyfile]
> unmanaged-devices=interface-name:^veth*;interface-name:${INTERFACE}
> EOF
~# systemctl restart NetworkManager
```
```shell
~# INTERFACE=<your_interface_name>
~# cat << EOF | > /etc/NetworkManager/conf.d/spidernet.conf
> [keyfile]
> unmanaged-devices=interface-name:^veth*;interface-name:${INTERFACE}
> EOF
~# systemctl restart NetworkManager
```

## Prerequisite

Expand Down

0 comments on commit b5c2a75

Please sign in to comment.