From d089c359094c79bb45ceb6911d24240d42447a2f Mon Sep 17 00:00:00 2001 From: Mengxin Liu Date: Thu, 2 Jan 2025 04:07:34 +0000 Subject: [PATCH] fix broken anchors Signed-off-by: Mengxin Liu --- docs/advance/vip.en.md | 2 +- docs/advance/with-bgp.md | 4 ++-- docs/advance/with-ovn-ic.md | 18 +++++++++--------- docs/guide/subnet.en.md | 2 +- docs/guide/vpc.en.md | 2 +- 5 files changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/advance/vip.en.md b/docs/advance/vip.en.md index 3705a48c4..aa48dba30 100644 --- a/docs/advance/vip.en.md +++ b/docs/advance/vip.en.md @@ -223,4 +223,4 @@ spec: Due to the particularity of 'StatefulSet' and 'VM', after their Pod is destroyed and pulled up, it will re-use the previously set VIP. -VM retention VIP needs to ensure that 'kube-ovn-controller' 'keep-vm-ip' parameter is' true '. Please refer to [Kubevirt VM enable keep its ip](../guide/setup-options.en.md#kubevirt-vm) +VM retention VIP needs to ensure that 'kube-ovn-controller' 'keep-vm-ip' parameter is' true '. Please refer to [Kubevirt VM enable keep its ip](../guide/setup-options.en.md#kubevirt-vm-fixed-address-settings) diff --git a/docs/advance/with-bgp.md b/docs/advance/with-bgp.md index 211f641e7..cfa6f9fb1 100644 --- a/docs/advance/with-bgp.md +++ b/docs/advance/with-bgp.md @@ -3,7 +3,7 @@ Kube-OVN 支持将 Pods、Subnets、Services 和 EIPs 的 IP 地址通过 BGP 协议向外部进行路由广播，从而使得外部可以直接访问到集群内的 IP 地址。 如果需要使用该功能，需要在特定节点安装 `kube-ovn-speaker` 并对需要对外暴露的 Pod 或 Subnet 增加对应的 annotation。 -如果要在 EIP 上使用 BGP，需要使用特殊参数创建 VPC NAT Gateway，有关更多信息，请参阅[发布 EIPs](#发布-eips)。 +如果要在 EIP 上使用 BGP，需要使用特殊参数创建 VPC NAT Gateway，有关更多信息，请参阅[发布 EIPs](#eips)。 ## 安装 kube-ovn-speaker @@ -73,7 +73,7 @@ kubectl annotate pod sample ovn.kubernetes.io/bgp- kubectl annotate subnet ovn-default ovn.kubernetes.io/bgp- ``` -查看[发布策略](#发布策略)以了解如何通过设置注解来控制 BGP 对外发布策略。 +查看[发布策略](#_1)以了解如何通过设置注解来控制 BGP 对外发布策略。 ## 发布 `ClusterIP` 类型 Service 路由 diff --git a/docs/advance/with-ovn-ic.md b/docs/advance/with-ovn-ic.md index d20945005..4323188d2 100644 --- a/docs/advance/with-ovn-ic.md +++ b/docs/advance/with-ovn-ic.md @@ -254,13 +254,13 @@ switch da6138b8-de81-4908-abf9-b2224ec4edf3 (ts) 下面手动设置路由，在该例子中，集群 `az1` 内的子网 CIDR 为 `10.16.0.0/24`，集群 `az2` 内的子网 CIDR 为 `10.17.0.0/24`。 -在集群 `az1` 设置到集群 `az2` 的路由: +在集群 `az1` 设置到集群 `az2` 的路由： ```bash kubectl ko nbctl lr-route-add ovn-cluster 10.17.0.0/24 169.254.100.31 ``` -在集群 `az2` 设置到集群 `az1` 的路由: +在集群 `az2` 设置到集群 `az1` 的路由： ```bash kubectl ko nbctl lr-route-add ovn-cluster 10.16.0.0/24 169.254.100.79 @@ -272,7 +272,7 @@ kubectl ko nbctl lr-route-add ovn-cluster 10.16.0.0/24 169.254.100.79 优先推荐方案 1，Kube-OVN v1.11.16 之后支持。 -方法同[单节点部署方案 1](#单节点部署方案-1) +方法同[单节点部署方案 1](#1) ### 高可用部署方案 2 @@ -292,8 +292,8 @@ docker run --name=ovn-ic-db -d --env "ENABLE_OVN_LEADER_CHECK="false"" --network ctr -n k8s.io run -d --env "ENABLE_OVN_LEADER_CHECK="false"" --net-host --privileged --mount="type=bind,src=/etc/ovn/,dst=/etc/ovn,options=rbind:rw" --mount="type=bind,src=/var/run/ovn,dst=/var/run/ovn,options=rbind:rw" --mount="type=bind,src=/var/log/ovn,dst=/var/log/ovn,options=rbind:rw" --env="NODE_IPS="192.168.65.3,192.168.65.2,192.168.65.1"" --env="LOCAL_IP="192.168.65.3"" docker.io/kubeovn/kube-ovn:{{ variables.version }} ovn-ic-db bash start-ic-db.sh ``` -- `LOCAL_IP`： 当前容器所在节点 IP 地址。 -- `NODE_IPS`： 运行 `OVN-IC` 数据库的三个节点 IP 地址，使用逗号进行分隔。 +- `LOCAL_IP`：当前容器所在节点 IP 地址。 +- `NODE_IPS`：运行 `OVN-IC` 数据库的三个节点 IP 地址，使用逗号进行分隔。 接下来，在另外两个节点部署 `OVN-IC` 数据库的 follower。 @@ -309,8 +309,8 @@ docker run --name=ovn-ic-db -d --network=host --privileged -v /etc/ovn/:/etc/ovn ctr -n k8s.io run -d --net-host --privileged --mount="type=bind,src=/etc/ovn/,dst=/etc/ovn,options=rbind:rw" --mount="type=bind,src=/var/run/ovn,dst=/var/run/ovn,options=rbind:rw" --mount="type=bind,src=/var/log/ovn,dst=/var/log/ovn,options=rbind:rw" --env="NODE_IPS="192.168.65.3,192.168.65.2,192.168.65.1"" --env="LOCAL_IP="192.168.65.2"" --env="LEADER_IP="192.168.65.3"" docker.io/kubeovn/kube-ovn:{{ variables.version }} ovn-ic-db bash start-ic-db.sh ``` -- `LOCAL_IP`： 当前容器所在节点 IP 地址。 -- `NODE_IPS`： 运行 `OVN-IC` 数据库的三个节点 IP 地址，使用逗号进行分隔。 +- `LOCAL_IP`：当前容器所在节点 IP 地址。 +- `NODE_IPS`：运行 `OVN-IC` 数据库的三个节点 IP 地址，使用逗号进行分隔。 - `LEADER_IP`: 运行 `OVN-IC` 数据库 leader 节点的 IP 地址。 在每个集群创建 `ovn-ic-config` 时指定多个 `OVN-IC` 数据库节点地址： @@ -333,9 +333,9 @@ data: ## 支持集群互联 ECMP -前提控制器是按照[单节点部署方案 1](#单节点部署方案-1)部署 +前提控制器是按照[单节点部署方案 1](#1)部署 -该方案默认支持集群互联 ECMP，ECMP path 默认为 3，同时也支持修改 ECMP path 条数，使用命令: +该方案默认支持集群互联 ECMP，ECMP path 默认为 3，同时也支持修改 ECMP path 条数，使用命令： ```bash kubectl edit deployment ovn-ic-server -n kube-system diff --git a/docs/guide/subnet.en.md b/docs/guide/subnet.en.md index fd5399969..b5bbc2899 100644 --- a/docs/guide/subnet.en.md +++ b/docs/guide/subnet.en.md @@ -140,7 +140,7 @@ EOF - `excludeIps`: The address list is reserved so that the container network will not automatically assign addresses in the list, which can be used as a fixed IP address assignment segment or to avoid conflicts with existing devices in the physical network in Underlay mode. - `gateway`：For this subnet gateway address, Kube-OVN will automatically assign the corresponding logical gateway in Overlay mode, and the address should be the underlying physical gateway address in Underlay mode. - `namespaces`: Bind the list of Namespace for this Subnet. Pods under the Namespace will be assigned addresses from the current Subnet after binding. -- `routeTable`: Associate the route table, default is main table, route table definition please defer to [Static Routes](vpc.en.md#_3) +- `routeTable`: Associate the route table, default is main table, route table definition please defer to [Static Routes](vpc.en.md#static-routes) ### Create Pod in the Subnet diff --git a/docs/guide/vpc.en.md b/docs/guide/vpc.en.md index bf87d479c..e2807097a 100644 --- a/docs/guide/vpc.en.md +++ b/docs/guide/vpc.en.md @@ -366,7 +366,7 @@ spec: - `policy`: Supports destination routing `policyDst` and source routing `policySrc`. - When there are overlapping routing rules, the rule with the longer CIDR mask has higher priority, and if the mask length is the same, the destination route has a higher priority over the source route. -- `routeTable`: You can store the route in specific table, default is main table. Associate with subnet please defer to [Create Custom Subnets](subnet.en.md/#_5) +- `routeTable`: You can store the route in specific table, default is main table. Associate with subnet please defer to [Create Custom Subnets](subnet.en.md/#create-custom-subnets) ### Policy Routes