Milvus Helm chart issue: connection refused / i/o timeout and Attu Deadline exceeded

Products

• Bitnami Premium (Bitnami Secure Images)

Issue/Introduction

The streaming node listens on dynamically assigned gRPC ports, while the chart’s streaming node NetworkPolicy only allows the configured port (e.g. 19530). That blocks coordinator/query-node → streaming node traffic and leads to connection refused / i/o timeout and Attu Deadline exceeded.

Cause

According to the milvus source code, random port assignment occurs when there is an issue allocating the port set in the configuration. It is possible that this could be a kernel limitation or kubelet directive of your Kubernetes platform.

Resolution

As a workaround, you can set this in the values.yaml:

streamingNode:
  networkPolicy:
    extraIngress:
      - from:
          - podSelector:
              matchLabels:
                app.kubernetes.io/part-of: milvus

This should allow the communication to any port from any milvus component to the streaming node.

 

Should you find any schema validation issue, please deploy with --skip-schema-validation (this won't be necessary in a future version of the chart).