Skip to content

Commit

Permalink
fix typos (#2815)
Browse files Browse the repository at this point in the history
  • Loading branch information
wangzihao05 committed May 16, 2023
1 parent fca6c9d commit 0466edc
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/cluster-submariner.md
Expand Up @@ -99,15 +99,15 @@ ports:
protocol: TCP
```

`11.16.0.12` is the IP address of the pod for this service `nginx` in another cluster. When this pod from another cluster is rebuilt, the new pod IP should be passed to this cluster, So that the new correct data path could be established. This whole process may takes some time, depending on your network and load.
`11.16.0.12` is the IP address of the pod for this service `nginx` in another cluster. When this pod from another cluster is rebuilt, the new pod IP should be passed to this cluster, so that the new correct data path could be established. This whole process may takes some time, depending on your network and load.

Besides, submariner now **do not** support the existence of multiple service CIDR or pod CIDR in a cluster.

#### Data Plane:

Submariner supports custom build handlers for different CNIs.

Currently the default data path is is used in this doc. Between the gateway nodes of clusters, traffic is encapsulated in a IPsec tunnel. For a work node, the traffic destined to a remote cluster will be transited through VXLAN tunnel(if `vx-submarine`) to the gateway node first.
Currently the default data path is used in this doc. Between the gateway nodes of clusters, traffic is encapsulated in a IPsec tunnel. For a work node, the traffic destined to a remote cluster will be transited through VXLAN tunnel(if `vx-submarine`) to the gateway node first.

#### operations:

Expand Down
2 changes: 1 addition & 1 deletion docs/multi-nic.md
Expand Up @@ -5,7 +5,7 @@ From v1.1, the IPAM part of Kube-OVN can provide subnet and static ip allocation
## How it works

By using [Intel Multus CNI](https://github.com/intel/multus-cni), we can attach multiple network interfaces into a Kubernetes Pod.
However, we still need some cluster-wide IPAM utilities to manage IP addresses for multi network to better mange other CNI plugins.
However, we still need some cluster-wide IPAM utilities to manage IP addresses for multi network to better manage other CNI plugins.
In Kube-OVN, we already have CRDs like Subnet and IP and functions for advanced IPAM like ip reservation, random allocation, static allocation and so on.
We extend the Subnet to network providers other than ovn, so other CNI plugins can take use all the IPAM functions already exist in Kube-OVN.

Expand Down

0 comments on commit 0466edc

Please sign in to comment.