qdrant / qdrant/qdrant-helm

No way to configure headless service independently from the main service

Open
#445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
191
Forks
98
Avg merge
2d 4h
Merged PRs (30d)
6

Description

Problem

The headless service (qdrant-headless) is fully derived from service.* values — there are no dedicated headlessService.* values to override its configuration independently. There is also no way to disable it entirely.

Currently service-headless.yaml reuses service.annotations, service.additionalLabels, and service.ports without any way to override or suppress them for the headless service specifically.

The headless service is only useful in cluster mode (config.cluster.enabled: true). When running a single-node Qdrant instance, it serves no purpose but still gets created unconditionally.

Expected behavior

Add a headlessService section in values.yaml that allows independent configuration and the ability to disable it entirely:

headlessService:
  enabled: true  # set to false to skip creating the headless service
  annotations: {}
  additionalLabels: {}

When annotations/additionalLabels are set, they should take precedence over the corresponding service.* values for the headless service.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read values.yaml and service-headless.yaml first to trace how the headless service currently reuses service.* values. Add the documented headlessService settings so the resource can be disabled and its annotations and labels can override service values; done means the independent configuration and disabled case are represented in the chart behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm
Domain
devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.