• 情况 *

我想有一个pool的serving pod（假设我有50个serving pod）。它们将通过LoadBalancer服务公开。
我想确保：
1.每个pod只为一个TCP连接服务，并保持该连接活动，直到客户端终止它。直到该pod的生命周期结束，它将不会接收任何其他TCP连接。
1.一旦客户端终止连接，pod就会清理并自行销毁。
1.另一个pod被旋转以匹配所需的副本号。由于它当前没有服务任何TCP连接，因此可以选择它来服务进入LoadBalancer服务的下一个TCP连接。

• 示例 *

1. Initially, a `Deployment` specifies a pool of 2 pods behind a LoadBalancer Service.

[1] [2]

------LoadBalancer-------


2. A client initiates a TCP connection to the LoadBalancer (e.g. telnet loadbalancer.domain.com 80) and the TCP connection is routed to the first vacant pod.

[1] [2]
 |
 |
------LoadBalancer-------
 |
 |
cl1


3. 24 hours after that (assuming data has been passing between client1 & pod1), another client hits to the same Load Balancer public domain. Since pod1 is serving client1, I want the second client to be routed to another vacant pod, such as pod 2.

[1] [2]
 |   |
 |   |
------LoadBalancer-------
 |   |
 |   |
cl1 cl2


4. 24 hours after that, client 1 terminates the connection, I want pod1 to do clean up and destroy itself shortly afterwards. No new connections should be routed to it. That leaves pod2 the only one still running.

[2]
 |
 |
------LoadBalancer-------
 |
 |
cl2


5. `Deployment` will create additional pods to ensure the number of replicas. So pod3 is created.

[1] [3]
 |   
 |   
------LoadBalancer-------
 |   
 |   
cl1 


6. Another client hits the same endpoint and is routed to a vacant pod (pod 3 in this case).

[1] [3]
 |   |
 |   |
------LoadBalancer-------
 |   |
 |   |
cl1 cl3

And so on and so forth.

字符串
有谁知道如何在K8上解决这个问题？