How to config rollingUpdate strategy

[douglarek]

Is there a way to configure the rollingUpdate strategy for the querynode deployment separately in the milvus-operator? In cases where there are a large number of queryNode pods with high memory usage, a maxSurge of 25% causes significant resource fluctuations in the cluster.

[douglarek]

Is there a way to configure the rollingUpdate strategy for the querynode deployment separately in the milvus-operator? In cases where there are a large number of queryNode pods with high memory usage, a maxSurge of 25% causes significant resource fluctuations in the cluster.

default settings in queryNode deployment:

strategy:
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 0
  type: RollingUpdate

[douglarek]

I noticed that in commit 242f4d4 of version 0.9, it was changed to a more conservative 1. Can this parameter be exposed later?

[haorenfsa]

@douglarek No for now, but maybe yes in Milvus v2.4 or v2.5. That's mainly because the k8s deployment controller won't respect the terminating pods when rolling kubernetes/kubernetes#107920, which is crucial for the rolling progress of Milvus.
Please note that milvus-operator now uses 2 deployment for rolling. So the normal strategy for deployment won't work. The @zilliztech/milvus team insists on keep rolling 1 at a time for the time being in order to ensure the availability.