You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/zh/docs/concepts/services-networking/dual-stack.md
+42-11Lines changed: 42 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ The following prerequisites are needed in order to utilize IPv4/IPv6 dual-stack
78
78
Kubernetes versions, refer to the documentation for that version
79
79
of Kubernetes.
80
80
* Provider support for dual-stack networking (Cloud provider or otherwise must be able to provide Kubernetes nodes with routable IPv4/IPv6 network interfaces)
81
-
* A [network plugin](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) that supports dual-stack networking
81
+
* A [network plugin](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) that supports dual-stack networking.
You can create {{< glossary_tooltip text="Services" term_id="service" >}} which can use IPv4, IPv6, or both.
148
+
You can create {{< glossary_tooltip text="Services" term_id="service" >}} which can use IPv4, IPv6, or both.
146
149
147
150
The address family of a Service defaults to the address family of the first service cluster IP range (configured via the `--service-cluster-ip-range` flag to the kube-apiserver).
148
151
@@ -195,7 +198,6 @@ You can set `.spec.ipFamilies` to any of the following array values:
195
198
- `["IPv6"]`
196
199
- `["IPv4","IPv6"]` (dual stack)
197
200
- `["IPv6","IPv4"]` (dual stack)
198
-
199
201
-->
200
202
-`["IPv4"]`
201
203
-`["IPv6"]`
@@ -224,14 +226,13 @@ These examples demonstrate the behavior of various dual-stack Service configurat
224
226
<!--
225
227
1. This Service specification does not explicitly define `.spec.ipFamilyPolicy`. When you create this Service, Kubernetes assigns a cluster IP for the Service from the first configured `service-cluster-ip-range` and sets the `.spec.ipFamilyPolicy` to `SingleStack`. ([Services without selectors](/docs/concepts/services-networking/service/#services-without-selectors) and [headless Services](/docs/concepts/services-networking/service/#headless-services) with selectors will behave in this same way.)
@@ -274,7 +275,7 @@ These examples demonstrate the behavior of various dual-stack Service configurat
274
275
#### 现有服务的双栈默认值
275
276
276
277
<!--
277
-
These examples demonstrate the default behavior when dual-stack is newly enabled on a cluster where Services already exist. (Upgrading an existing cluster to 1.21 or beyond will enable dual-stack.)
278
+
These examples demonstrate the default behavior when dual-stack is newly enabled on a cluster where Services already exist. (Upgrading an existing cluster to 1.21 or beyond will enable dual-stack.)
278
279
-->
279
280
下面示例演示了在服务已经存在的集群上新启用双栈时的默认行为。
280
281
(将现有集群升级到 1.21 或者更高版本会启用双协议栈支持。)
@@ -296,7 +297,7 @@ These examples demonstrate the default behavior when dual-stack is newly enabled
296
297
```shell
297
298
kubectl get svc my-service -o yaml
298
299
```
299
-
300
+
300
301
```yaml
301
302
apiVersion: v1
302
303
kind: Service
@@ -341,7 +342,7 @@ These examples demonstrate the default behavior when dual-stack is newly enabled
341
342
```shell
342
343
kubectl get svc my-service -o yaml
343
344
```
344
-
345
+
345
346
```yaml
346
347
apiVersion: v1
347
348
kind: Service
@@ -361,7 +362,7 @@ These examples demonstrate the default behavior when dual-stack is newly enabled
0 commit comments