Immutable solution version
There is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file
Complete solution
Context
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.
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'. Closed as completed.
Evidence
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'.
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_roktq_5Y8clK-8UiTW82iw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">There is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file <span>— Vectle</span></a>