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-cn/docs/reference/kubernetes-api/service-resources/service-v1.md
+25-5Lines changed: 25 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,7 +228,7 @@ ServiceSpec 描述用户在服务上创建的属性。
228
228
*Atomic: will be replaced during a merge*
229
229
-->
230
230
231
-
**原子: 将在合并期间被替换**
231
+
**原子:将在合并期间被替换**
232
232
233
233
<!--
234
234
IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this service. This field is usually assigned automatically based on cluster configuration and the ipFamilyPolicy field. If this field is specified manually, the requested family is available in the cluster, and ipFamilyPolicy allows it, it will be used; otherwise creation of the service will fail. This field is conditionally mutable: it allows for adding or removing a secondary IP family, but it does not allow changing the primary IP family of the Service. Valid values are "IPv4" and "IPv6". This field only applies to Services of types ClusterIP, NodePort, and LoadBalancer, and does apply to "headless" services. This field will be wiped when updating a Service to type ExternalName.
@@ -287,7 +287,7 @@ ServiceSpec 描述用户在服务上创建的属性。
287
287
*Atomic: will be replaced during a merge*
288
288
-->
289
289
290
-
**原子: 将在合并期间被替换**
290
+
**原子:将在合并期间被替换**
291
291
292
292
<!--
293
293
ClusterIPs is a list of IP addresses assigned to this service, and are usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be empty) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above). Valid values are "None", empty string (""), or a valid IP address. Setting this to "None" makes a "headless service" (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required. Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName. If this field is not specified, it will be initialized from the clusterIP field. If this field is specified, clients must ensure that clusterIPs[0] and clusterIP have the same value.
@@ -490,13 +490,13 @@ ServiceSpec 描述用户在服务上创建的属性。
490
490
<!--
491
491
- **trafficDistribution** (string)
492
492
493
-
TrafficDistribution offers a way to express preferences for how traffic is distributed to Service endpoints. Implementations can use this field as a hint, but are not required to guarantee strict adherence. If the field is not set, the implementation will apply its default routing strategy. If set to "PreferClose", implementations should prioritize endpoints that are topologically close (e.g., same zone). This is an beta field and requires enabling ServiceTrafficDistribution feature.
493
+
TrafficDistribution offers a way to express preferences for how traffic is distributed to Service endpoints. Implementations can use this field as a hint, but are not required to guarantee strict adherence. If the field is not set, the implementation will apply its default routing strategy. If set to "PreferClose", implementations should prioritize endpoints that are topologically close (e.g., same zone). This is a beta field and requires enabling ServiceTrafficDistribution feature.
494
494
-->
495
495
-**trafficDistribution** (string)
496
496
497
497
trafficDistribution 提供了一种流量如何被分配到 Service 端点的偏好表达方式。
498
498
各个实现可以将此字段用作提示,但不需要严格遵守。如果此字段未设置,实现将应用其默认路由策略。
499
-
如果设置为“PreferClose”,则实现应优先考虑在拓扑上接近的端点(例如,位于同一区域)。
499
+
如果设置为“PreferClose”,则实现应优先考虑在拓扑上接近的端点(例如,位于同一区域)。
500
500
这是一个 Beta 字段,需要启用 ServiceTrafficDistribution 特性。
501
501
502
502
## ServiceStatus {#ServiceStatus}
@@ -523,7 +523,7 @@ ServiceStatus 表示 Service 的当前状态。
523
523
524
524
**补丁策略:基于键 `type` 合并**
525
525
526
-
**Map: 键类型的唯一值将在合并期间保留**
526
+
**Map:键类型的唯一值将在合并期间保留**
527
527
528
528
服务的当前状态。
529
529
@@ -688,8 +688,12 @@ ServiceStatus 表示 Service 的当前状态。
688
688
<aname="PortStatus"></a>
689
689
690
690
<!--
691
+
*PortStatus represents the error condition of a service port*
0 commit comments