Skip to content

Commit 3daefd5

Browse files
authored
Merge pull request #38074 from windsonsea/sernet
[zh] sync create-external-load-balancer.md
2 parents a061780 + 93036e9 commit 3daefd5

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

content/zh-cn/docs/tasks/access-application-cluster/create-external-load-balancer.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ nodes,
2525
_provided your cluster runs in a supported environment and is configured with
2626
the correct cloud load balancer provider package_.
2727
-->
28-
创建 {{< glossary_tooltip text="服务" term_id="service" >}} 时,你可以选择自动创建云网络负载均衡器。
28+
创建{{< glossary_tooltip text="服务" term_id="service" >}}时,你可以选择自动创建云网络负载均衡器。
2929
负载均衡器提供外部可访问的 IP 地址,可将流量发送到集群节点上的正确端口上
30-
**假设集群在支持的环境中运行,并配置了正确的云负载均衡器驱动包**)。
30+
**假设集群在支持的环境中运行,并配置了正确的云负载均衡器驱动包**)。
3131

3232
<!--
3333
You can also use an {{< glossary_tooltip term_id="ingress" >}} in place of Service.
@@ -265,20 +265,19 @@ Internal pod to pod traffic should behave similar to ClusterIP services, with eq
265265

266266
<!--
267267
## Garbage Collecting Load Balancers
268+
-->
269+
## 回收负载均衡器 {#garbage-collecting-load-balancers}
268270

269271
{{< feature-state for_k8s_version="v1.17" state="stable" >}}
270272

273+
<!--
271274
In usual case, the correlating load balancer resources in cloud provider should
272275
be cleaned up soon after a LoadBalancer type Service is deleted. But it is known
273276
that there are various corner cases where cloud resources are orphaned after the
274277
associated Service is deleted. Finalizer Protection for Service LoadBalancers was
275278
introduced to prevent this from happening. By using finalizers, a Service resource
276279
will never be deleted until the correlating load balancer resources are also deleted.
277280
-->
278-
## 回收负载均衡器 {#garbage-collecting-load-balancers}
279-
280-
{{< feature-state for_k8s_version="v1.17" state="stable" >}}
281-
282281
在通常情况下,应在删除 LoadBalancer 类型 Service 后立即清除云服务供应商中的相关负载均衡器资源。
283282
但是,众所周知,在删除关联的服务后,云资源被孤立的情况很多。
284283
引入了针对服务负载均衡器的终结器保护,以防止这种情况发生。
@@ -321,11 +320,10 @@ Kubernetes 控制平面自动创建外部负载均衡器、健康检查(如果
321320
## {{% heading "whatsnext" %}}
322321

323322
<!--
323+
* Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial
324324
* Read about [Service](/docs/concepts/services-networking/service/)
325325
* Read about [Ingress](/docs/concepts/services-networking/ingress/)
326-
* Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)
327326
-->
327+
* 遵循教程[使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/)
328328
* 阅读[服务](/zh-cn/docs/concepts/services-networking/service/)
329329
* 阅读 [Ingress](/zh-cn/docs/concepts/services-networking/ingress/)
330-
* 阅读[使用 Service 连接到应用](/zh-cn/docs/concepts/services-networking/connect-applications-service/)
331-

0 commit comments

Comments
 (0)