I follow this link to install milvus cluster. When I execute this command "helm install my-release milvus/milvus" ,I find that a pod never started successfully. enter image description here

$ kubectl get pod | grep lcl
lcl-release-milvus-querynode-56b9b4d54d-9r7jl      0/1     Pending            0                6h31m here

Then I use "kubectl describe pods lcl-release-milvus-querynode-56b9b4d54d-9r7jl" to get the following info.

$ kubectl describe pods lcl-release-milvus-querynode-56b9b4d54d-9r7j
0/4 nodes are available: 4 node(s) didn't satisfy existing pods anti-affinity rules.

Who can help me analyze the problem?

CodePudding user response：

Base on the milvus chart, only the etcd has the affinity setup, but your "queryNode" also has the affinity set? You need to remove the affinity that you have set here for queryNode.