@@ -27,7 +27,7 @@ Service 连接到了你的应用,你就有了一个持续运行的多副本应
27
27
<!--
28
28
## Termination process for Pods and their endpoints
29
29
30
- There are often cases when you need to terminate a Pod - be it for upgrade or scale down.
30
+ There are often cases when you need to terminate a Pod - be it to upgrade or scale down.
31
31
In order to improve application availability, it may be important to implement
32
32
a proper active connections draining.
33
33
@@ -48,12 +48,12 @@ a simple nginx web server to demonstrate the concept.
48
48
<!--
49
49
## Example flow with endpoint termination
50
50
51
- The following is the example of the flow described in the
51
+ The following is the example flow described in the
52
52
[Termination of Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)
53
53
document.
54
54
55
- Let's say you have a Deployment containing of a single `nginx` replica
56
- (just for demonstration purposes) and a Service:
55
+ Let's say you have a Deployment containing a single `nginx` replica
56
+ (say just for the sake of demonstration purposes) and a Service:
57
57
-->
58
58
## 端点终止的示例流程 {#example-flow-with-endpoint-termination}
59
59
@@ -223,14 +223,14 @@ The output is similar to this:
223
223
224
224
<!--
225
225
This allows applications to communicate their state during termination
226
- and clients (such as load balancers) to implement a connections draining functionality.
226
+ and clients (such as load balancers) to implement connection draining functionality.
227
227
These clients may detect terminating endpoints and implement a special logic for them.
228
228
-->
229
229
这种设计使得应用可以在终止期间公布自己的状态,而客户端(如负载均衡器)则可以实现连接排空功能。
230
230
这些客户端可以检测到正在终止的端点,并为这些端点实现特殊的逻辑。
231
231
232
232
<!--
233
- In Kubernetes, endpoints that are terminating always have their `ready` status set as as `false`.
233
+ In Kubernetes, endpoints that are terminating always have their `ready` status set as `false`.
234
234
This needs to happen for backward
235
235
compatibility, so existing load balancers will not use it for regular traffic.
236
236
If traffic draining on terminating pod is needed, the actual readiness can be
0 commit comments