Skip to content

Commit 16a725f

Browse files
committed
[zh-cn]sync services-networking/service.md
Signed-off-by: xin.li <[email protected]>
1 parent 87b867b commit 16a725f

File tree

1 file changed

+7
-4
lines changed
  • content/zh-cn/docs/concepts/services-networking

1 file changed

+7
-4
lines changed

content/zh-cn/docs/concepts/services-networking/service.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,10 @@ weight: 10
2626

2727
<!-- overview -->
2828

29+
<!--
2930
{{< glossary_definition term_id="service" length="short" >}}
31+
-->
32+
{{< glossary_definition term_id="service" length="short" prepend="Kubernetes 中 Service 是" >}}
3033

3134
<!--
3235
A key aim of Services in Kubernetes is that you don't need to modify your existing
@@ -1091,14 +1094,14 @@ by making the changes that are equivalent to you requesting a Service of
10911094
`type: NodePort`. The cloud-controller-manager component then configures the external load balancer to
10921095
forward traffic to that assigned node port.
10931096

1094-
_As an alpha feature_, you can configure a load balanced Service to
1097+
You can configure a load balanced Service to
10951098
[omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the
10961099
cloud provider implementation supports this.
10971100
-->
10981101
要实现 `type: LoadBalancer` 的服务,Kubernetes 通常首先进行与请求 `type: NodePort` 服务等效的更改。
10991102
cloud-controller-manager 组件然后配置外部负载均衡器以将流量转发到已分配的节点端口。
11001103

1101-
**作为 Alpha 特性**,你可以将负载均衡服务配置为[忽略](#load-balancer-nodeport-allocation)分配节点端口,
1104+
你可以将负载均衡服务配置为[忽略](#load-balancer-nodeport-allocation)分配节点端口,
11021105
前提是云提供商实现支持这点。
11031106

11041107
{{< note >}}
@@ -1810,7 +1813,7 @@ will be routed to one of the Service endpoints. `externalIPs` are not managed by
18101813
of the cluster administrator.
18111814

18121815
In the Service spec, `externalIPs` can be specified along with any of the `ServiceTypes`.
1813-
In the example below, "`my-service`" can be accessed by clients on "`80.11.12.10:80`" (`externalIP:port`)
1816+
In the example below, "`my-service`" can be accessed by clients on "198.51.100.32:80`" (`externalIP:port`)
18141817
-->
18151818
### 外部 IP {#external-ips}
18161819

@@ -1820,7 +1823,7 @@ In the example below, "`my-service`" can be accessed by clients on "`80.11.12.10
18201823
`externalIPs` 不会被 Kubernetes 管理,它属于集群管理员的职责范畴。
18211824

18221825
根据 Service 的规定,`externalIPs` 可以同任意的 `ServiceType` 来一起指定。
1823-
在上面的例子中,`my-service` 可以在 "`80.11.12.10:80`" (`externalIP:port`) 上被客户端访问。
1826+
在上面的例子中,`my-service` 可以在 "`198.51.100.32:80`" (`externalIP:port`) 上被客户端访问。
18241827

18251828
```yaml
18261829
apiVersion: v1

0 commit comments

Comments
 (0)