Component

core/datastore/qdrant

A Qdrant vector database. Stores embedding vectors alongside their payloads and answers nearest-neighbour queries over them, so an application that retrieves reference material by similarity is wired to this component rather than to a general-purpose store. Collections are created through Qdrant's own API at runtime; the component declares the server, not its contents. It is realized on Kubernetes and, for local development, on Docker Compose, and exports its host, its HTTP port and its gRPC port to consumers via the uses topology. On Kubernetes there are two realizations and the Manifest chooses between them. `qdrant` synthesizes the server as a workload and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `qdrant-chart` renders the product's own Helm chart, which additionally carries its maintainers' start-up script, data-volume ownership step and pre-stop pause, so reach for it where a chart repository is reachable at build time. That chart also renders an interaction check — a Pod annotated as a test hook, whose script deletes and recreates a collection named `test_collection` on the running server — which the chart offers no setting to decline; the chart realization's own description states what it does and when it runs. While api_key is filled, a scrape of `metrics_endpoint` presents on its connection's `credential` the key attached to read_only_api_key, or the api_key where that slot is empty. The read-only key still reads every collection: it makes a scraper read-only, not metrics-only. `aggrega lint --release` reports such a credential as differing from api_key, as expected.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:b0961eaec3c3ddc6f6ae0d3771b7faaa9af174699cd4091865afdbcc336888f3
Published
2026-11-10T10:11:02Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:3956ba12160a8653d222816071fc47fb42e4a1f7aefcef46cba0d66eb1ad3db5

Reference at this version

oci://hub.aggrega.ai/component/core/datastore/qdrant:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
log_levelstring—noServer log verbosity (TRACE, DEBUG, INFO, WARN or ERROR). Omit to use the server default (INFO).
max_request_size_mbinteger (min 1)—noLargest request body the server accepts, in mebibytes. Omit to use the server default (32).
telemetry_disabledbooleanfalsenoStop the server reporting anonymous usage telemetry to its maintainers. Off by default, matching the server's own default.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
portinteger (min 1024, max 65535)6333noHTTP (REST) listen port. Most operators should omit this and let the Recipe assign the default (6333).
grpc_portinteger (min 1024, max 65535)6334nogRPC listen port, published alongside the HTTP port for clients that prefer it. Most operators should omit this and let the Recipe assign the default (6334).
engine_versionstringv1.19.0noQdrant container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag.
source_versionstring—noVersion of the Helm chart the chart-backed realization pulls. Read only by that realization; the workload-synthesis and Compose realizations pull no source artifact and ignore it. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart.
computeobject—no—
storageobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name of the Service fronting the vector database. A consumer dials this name together with whichever of the two published ports its client speaks.
portinteger—yesTCP port the REST API is served on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
grpc_portinteger—noTCP port the gRPC API is served on, published beside the REST port for a client that prefers it. It is a second listener on the same server, not an alternative address.
protocolstring—noHow the published address is spoken to on `port` — `http`, so a consumer reaching the REST API composes its address on that scheme.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics`, on the REST port. While the api_key slot is filled the server answers it only to a key it holds, so a scrape presents one on its connection's `credential` slot: the read-only key where read_only_api_key is filled, and the api_key otherwise.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

SlotSelectorRequiredInjectSensitiveDescription
api_keyfeature.aggrega.ai/kind=secretnoenvyesOptional service API-key credential. When attached, every request to the server must present this key, or for a read the key attached to read_only_api_key; unattached, the server accepts unauthenticated requests.
read_only_api_keyfeature.aggrega.ai/kind=secretnoenvyesOptional read-only API key, filled beside api_key. When attached, the server also accepts this key and answers it with read access to every collection and to its metrics, refusing any write made with it; a scrape of metrics_endpoint presents it in place of api_key, and `aggrega lint --release` then reports that scrape's credential as differing from api_key, which is expected, since the server holds both keys. Filled without api_key, the build halts.

Self-inject allowlist

env

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy