Skip to content

Is Headless Service exposure of gRPC port necessary for Qdrant? #326

@sjkim2322

Description

@sjkim2322

Question: Is Headless Service exposure of gRPC port necessary for Qdrant?

Hi Qdrant team,

I’m deploying Qdrant using the official Helm chart, and I’ve noticed that the gRPC port (default: 6334) is exposed not only via a LoadBalancer service but also via a Headless Service.

Since intra-cluster communication (e.g. Raft replication) uses the P2P port, and client communication typically goes through the LoadBalancer, I’m wondering:

  • Is there any specific reason why the gRPC port is exposed via the Headless Service?
  • Is it required for any internal use cases (like health probes, node-to-node gRPC calls, etc.)?
  • If not mandatory, would it be safe to disable gRPC exposure in the Headless Service?

Thanks in advance! Really appreciate your work on Qdrant.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions