我们希望在openshift部署的所有Pod中轮流请求。
我已经在Route config中配置了以下注释，但是对所有Pod的调用顺序是随机的:
haproxy.router.openshift.io/balance : roundrobin
haproxy.router.openshift.io/disable_cookies: 'true'
我们有3个旋转包。我们希望请求具有顺序
pod1，pod2，pod3，pod1，pod2，pod3，pod1 ....
但是随机设置以上注释后的实际行为如下:
pod1，pod1，pod2，pod2，pod3，pod1，pod2，pod2 ....
我们是否需要配置任何openshift配置使其完美地轮循？
最佳答案
如果要按顺序通过pod1，pod2，pod3访问，则应在同一Pod组上使用leastconn。
leastconn The server with the lowest number of connections receives the
connection. Round-robin is performed within groups of servers
of the same load to ensure that all servers will be used. Use
of this algorithm is recommended where very long sessions are
expected, such as LDAP, SQL, TSE, etc... but is not very well
suited for protocols using short sessions such as HTTP. This
algorithm is dynamic, which means that server weights may be
adjusted on the fly for slow starts for instance.
roundrobin的HAProxy将平均分配请求，但可能无法保护组中的访问服务器顺序。roundrobin Each server is used in turns, according to their weights.
This is the smoothest and fairest algorithm when the server's
processing time remains equally distributed. This algorithm
is dynamic, which means that server weights may be adjusted
on the fly for slow starts for instance. It is limited by
design to 4095 active servers per backend. Note that in some
large farms, when a server becomes up after having been down
for a very short time, it may sometimes take a few hundreds
requests for it to be re-integrated into the farm and start
receiving traffic. This is normal, though very rare. It is
indicated here in case you would have the chance to observe
it, so that you don't worry.
有关平衡算法选项的详细信息，请参考HAProxy balance (algorithm)。
关于cookies - 跨所有Pod的Openshift轮询请求，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/55549489/