Qdrant distributed-shard administration, cluster state, telemetry, health, metrics, service version, and issue operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 17 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.
What this pack installs
- qdrant-cluster-service Ingredient
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Destructive
Web APIs
qdrant-cluster-service
external change
Read: service.root · No approvalRead: distributed.cluster_status · Asks approvalDestructive: distributed.remove_peer · Always asksDestructive: distributed.recover_current_peer · Always asksRead: distributed.cluster_telemetry · Asks approvalRead: distributed.collection_cluster_info · Asks approvalAdmin: distributed.update_collection_cluster · Always asksRead: distributed.list_shard_keys · Asks approvalAdmin: distributed.create_shard_key · Always asksDestructive: distributed.delete_shard_key · Always asksRead: service.healthz · No approvalRead: beta.get_issues · Asks approvalDestructive: beta.clear_issues · Always asksRead: service.livez · No approvalRead: service.metrics · Asks approvalRead: service.readyz · No approvalRead: service.telemetry · Asks approval
Data it touches
SurfacesWeb APIs
Tags
pack:qdrantqdrantvector-databaseclusterservicediagnosticsapicomposition