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
addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name. (Deprecated) The EndpointSlice controller only generates, and kube-proxy only processes, slices of addressType "IPv4" and "IPv6". No semantics are defined for the "FQDN" type.
addresses of this endpoint. For EndpointSlices of addressType "IPv4" or "IPv6", the values are IP addresses in canonical form. The syntax and semantics of other addressType values are not defined. This must contain at least one address but no more than 100. EndpointSlices generated by the EndpointSlice controller will always have exactly 1 address. No semantics are defined for additional addresses beyond the first, and kube-proxy does not look at them.
ready indicates that this endpoint is ready to receive traffic, according to whatever system is managing the endpoint. A nil value should be interpreted as "true". In general, an endpoint should be marked ready if it is serving and not terminating, though this can be overridden in some cases, such as when the associated Service has set the publishNotReadyAddresses flag.
serving indicates that this endpoint is able to receive traffic, according to whatever system is managing the endpoint. For endpoints backed by pods, the EndpointSlice controller will mark the endpoint as serving if the pod's Ready condition is True. A nil value should be interpreted as "true".
147
149
-->
148
-
150
+
149
151
`serving` 表示此端点能够接收流量，根据管理端点的系统。对于由 Pod 支持的端点，
150
152
如果 Pod 的 Ready 条件为 True，EndpointSlice 控制器会将端点标记为 `serving`。
151
153
nil 值应解释为 "true"。
152
154
153
155
-**endpoints.conditions.terminating** (boolean)
154
-
156
+
155
157
<!--
156
158
terminating indicates that this endpoint is terminating. A nil value should be interpreted as "false".
deprecatedTopology contains topology information part of the v1beta1 API. This field is deprecated, and will be removed when the v1beta1 API is removed (no sooner than kubernetes v1.24). While this field can hold values, it is not writable through the v1 API, and any attempts to write to it will be silently ignored. Topology information can be found in the zone and nodeName fields instead.
166
168
-->
167
-
169
+
168
170
`deprecatedTopology` 包含 v1beta1 API 的拓扑信息部分。目前已经弃用了此字段，
hints contains information associated with how an endpoint should be consumed.
178
180
-->
179
-
181
+
180
182
`hints` 是关于应该如何使用某端点的提示信息。
181
183
182
184
<aname="EndpointHints"></a>
183
185
184
186
<!--
185
187
*EndpointHints provides hints describing how an endpoint should be consumed.*
186
188
-->
187
-
189
+
188
190
**EndpointHints 提供应该如何使用某端点的提示信息。**
189
191
190
192
-**endpoints.hints.forNodes** ([]ForNode)
191
193
192
194
<!--
193
195
*Atomic: will be replaced during a merge*
194
196
-->
195
-
197
+
196
198
**原子性：合并期间将被替换**
197
199
198
200
<!--
199
-
forNodes indicates the node(s) this endpoint should be consumed by when using topology aware routing. May contain a maximum of 8 entries. This is an Alpha feature and is only used when the PreferSameTrafficDistribution feature gate is enabled.
201
+
forNodes indicates the node(s) this endpoint should be consumed by when using topology aware routing. May contain a maximum of 8 entries.
hostname of this endpoint. This field may be used by consumers of endpoints to distinguish endpoints from each other (e.g. in DNS names). Multiple endpoints which use the same hostname should be considered fungible (e.g. multiple A values in DNS). Must be lowercase and pass DNS Label (RFC 1123) validation.
targetRef is a reference to a Kubernetes object that represents this endpoint.
275
276
-->
276
-
277
+
277
278
`targetRef` 是对代表此端点的 Kubernetes 对象的引用。
278
279
279
280
-**endpoints.zone** (string)
280
281
281
282
<!--
282
283
zone is the name of the Zone this endpoint exists in.
283
284
-->
284
-
285
+
285
286
`zone` 是此端点所在的可用区（Zone）的名称。
286
287
287
288
-**ports** ([]EndpointPort)
288
289
289
290
<!--
290
291
*Atomic: will be replaced during a merge*
291
292
-->
292
-
293
+
293
294
**原子性：合并期间会被替代**
294
-
295
+
295
296
<!--
296
297
ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. Each slice may include a maximum of 100 ports. Services always have at least 1 port, so EndpointSlices generated by the EndpointSlice controller will likewise always have at least 1 port. EndpointSlices used for other purposes may have an empty ports list.
*EndpointPort represents a Port used by an EndpointSlice*
309
310
-->
310
-
311
+
311
312
**EndpointPort 是 EndpointSlice 使用的端口。**
312
313
313
314
-**ports.port** (int32)
314
315
315
316
<!--
316
317
port represents the port number of the endpoint. If the EndpointSlice is derived from a Kubernetes service, this must be set to the service's target port. EndpointSlices used for other purposes may have a nil port.
name represents the name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is derived from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or '-'. * must start and end with an alphanumeric character. Default is empty string.
The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:
359
-
360
+
360
361
* Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).
361
-
362
+
362
363
* Kubernetes-defined prefixed names:
363
364
* 'kubernetes.io/h2c' - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior-
364
365
* 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
365
-
* 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
366
-
366
+
* 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
367
+
367
368
* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.
0 commit comments