There is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file

TL;DR

Implemented by maintainer timvisee: cluster bootstrap/topology configuration in the config file shipped first in the qdrant/qdrant:dev image and then in stable Qdrant 1.13.3. Reporter confirmed 'it works like a charm'.

The error

When deploying a multi-node Qdrant cluster with docker-compose / swarm / kubernetes, the initial cluster topology (bootstrap, peer URIs) could only be passed as CLI flags (--bootstrap, --uri), not configured in config.yaml, making containerized scaling awkward.

Fix

1. Implemented by maintainer timvisee: cluster bootstrap/topology configuration in the config file shipped first in the qdrant/qdrant:dev image and then in stable Qdrant 1.13.3.
2. Reporter confirmed 'it works like a charm'.
3. Closed as completed.

Success check: the symptom above is gone and the original operation completes.

When to use

• You hit this exact symptom in qdrant.
• You want the verified fix without digging through the thread.

When not to use

• A different error in qdrant, even a similar-looking one.
• General qdrant setup or credential questions.

Compatibility

• Qdrant (qdrant/qdrant)

Variant phrasings

• How to fix "there is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file" in qdrant
• qdrant: there is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file

Source

• https://github.com/qdrant/qdrant/issues/5880

In gh:qdrant/qdrant#5880 (https://github.com/qdrant/qdrant/issues/5880), the question was: When deploying a multi-node Qdrant cluster with docker-compose / swarm / kubernetes, the initial cluster topology (bootstrap, peer URIs) could only be passed as CLI flags (--bootstrap, --uri), not configured in config.yaml, making containerized scaling awkward. The verified resolution: Implemented by maintainer timvisee: cluster bootstrap/topology configuration in the config file shipped first in the qdrant/qdrant:dev image and then in stable Qdrant 1.13.3. Reporter confirmed 'it works like a charm'.