Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update: no need to add static route for custom vpc #151

Merged
merged 1 commit into from
Jan 25, 2024
Merged

update: no need to add static route for custom vpc #151

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 0 additions & 15 deletions docs/advance/ovn-eip-fip-snat.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,10 +255,6 @@ metadata:
spec:
namespaces:
- vpc1
staticRoutes: # configure routing rules: Which additional public network routes a subnet under the vpc needs to be based on needs to be added manually. The following example is for reference only. Users need to configure it according to their actual situation.
- cidr: 192.168.0.1/28
nextHopIP: 10.10.204.254
policy: policySrc
enableExternal: true # vpc enableExternal will automatically create an lrp association to the public network specified above
addExternalSubnets: # configure addExternalSubnets to support connecting multiple additional public networks
- extra
Expand All @@ -282,17 +278,6 @@ router 87ad06fd-71d5-4ff8-a1f0-54fa3bba1a7f (vpc1)
gateway chassis: [7cedd14f-265b-42e5-ac17-e03e7a1f2342 276baccb-fe9c-4476-b41d-05872a94976d fd9f140c-c45d-43db-a6c0-0d4f8ea298dd]
```

```bash
# k ko nbctl lr-route-list vpc1
IPv4 Routes
Route Table <main>:
192.168.0.1/28 10.10.204.254 src-ip
0.0.0.0/0 10.5.204.254 dst-ip
# The route currently supports automatic maintenance
# Additional public networks require manual routing configuration in the vpc. In the above example, the source IP address is 192.168.0.1/28 and will be forwarded to the additional public network.
# Users can manually configure routing rules according to the situation
```

## 2. ovn-eip

This function is designed and used in the same way as iptables-eip, ovn-eip currently has three types
Expand Down
15 changes: 0 additions & 15 deletions docs/advance/ovn-eip-fip-snat.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,10 +253,6 @@ metadata:
spec:
namespaces:
- vpc1
staticRoutes: # 配置路由规则：vpc 下的某个子网需要基于哪一个额外的公网网络的路由需要手动添加，以下示例仅供参考，用户需根据自己的实际情况进行配置
- cidr: 192.168.0.1/28
nextHopIP: 10.10.204.254
policy: policySrc
enableExternal: true # 开启 enableExternal 后 vpc 会自动连接名为 external 的 ls
addExternalSubnets: # 配置 addExternalSubnets 支持连接多个额外的公网网络
- extra
Expand All @@ -280,17 +276,6 @@ router 87ad06fd-71d5-4ff8-a1f0-54fa3bba1a7f (vpc1)
gateway chassis: [7cedd14f-265b-42e5-ac17-e03e7a1f2342 276baccb-fe9c-4476-b41d-05872a94976d fd9f140c-c45d-43db-a6c0-0d4f8ea298dd]
```

```bash
# k ko nbctl lr-route-list vpc1
IPv4 Routes
Route Table <main>:
192.168.0.1/28 10.10.204.254 src-ip
0.0.0.0/0 10.5.204.254 dst-ip
# 目前会为默认公网网络配置默认路由
# 额外公网网络需要在 vpc 手动配置路由，上述实例中源 IP 地址为 192.168.0.1/28 会转发至额外公网网络
# 用户可根据情况手动配置路由规则
```

## 2. ovn-eip

该功能和 iptables-eip 设计和使用方式基本一致，ovn-eip 目前有三种 type
Expand Down