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.
Procedencia
- Digest del contenido
- sha256:b0961eaec3c3ddc6f6ae0d3771b7faaa9af174699cd4091865afdbcc336888f3
- Publicado
- 2026-11-10T10:11:02Z
- Identidad de firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Oficialapplication/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
Referencia en esta versión
oci://hub.aggrega.ai/component/core/datastore/qdrant:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| log_level | string | — | no | Server log verbosity (TRACE, DEBUG, INFO, WARN or ERROR). Omit to use the server default (INFO). |
| max_request_size_mb | integer (min 1) | — | no | Largest request body the server accepts, in mebibytes. Omit to use the server default (32). |
| telemetry_disabled | boolean | false | no | Stop the server reporting anonymous usage telemetry to its maintainers. Off by default, matching the server's own default. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 6333 | no | HTTP (REST) listen port. Most operators should omit this and let the Recipe assign the default (6333). |
| grpc_port | integer (min 1024, max 65535) | 6334 | no | gRPC 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_version | string | v1.19.0 | no | Qdrant container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag. |
| source_version | string | — | no | Version 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. |
| compute | object | — | no | — |
| storage | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Contrato de salida
Valores que este componente publica para los consumidores a través de la topología uses.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| host | string | — | sí | In-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. |
| port | integer | — | sí | TCP 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_port | integer | — | no | TCP 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. |
| protocol | string | — | no | How the published address is spoken to on `port` — `http`, so a consumer reaching the REST API composes its address on that scheme. |
| metrics_endpoint | string | — | no | The 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. |
Sockets uses
Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.
No se declararon sockets uses.
Slots de acoplamiento
Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| api_key | feature.aggrega.ai/kind=secret | no | env | sí | Optional 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_key | feature.aggrega.ai/kind=secret | no | env | sí | Optional 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. |
Lista de permitidos de autoinyección
env
Relaciones
Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.
Usa
Esta entidad no usa nada del catálogo.
Usado por
usa el socket «backend»
usa el socket «cache»
usa el socket «queue»
usa el socket «backend»
usa el socket «cache»
usa el socket «queue»
usa el socket «backend»
usa el socket «backend»
usa el socket «cache»
usa el socket «queue»
usa el socket «backend»
usa el socket «cache»
usa el socket «queue»
usa el socket «backend»
usa el socket «cache»
usa el socket «queue»
usa el socket «knowledge_base»
usa el socket «backend»
usa el socket «cache»
usa el socket «vector_store»
usa el socket «backend»
usa el socket «cache»
usa el socket «vector_store»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «vector_store»
usa el socket «backend»
usa el socket «cache»
usa el socket «vector_store»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «state_store»
usa el socket «vector_store»
usa el socket «vector_store»
usa el socket «task_memory»
usa el socket «document_store»
usa el socket «vector_store»
usa el socket «vector_store»
usa el socket «checkpointer_db»
usa el socket «checkpointer_db»
usa el socket «backend»
usa el socket «backend»
usa el socket «backend»
usa el socket «vector_store»
usa el socket «vector_store»
usa el socket «storage»
usa el socket «knowledge_base»
usa el socket «data_store»
usa el socket «metadata_store»
usa el socket «target_datastore»
usa el socket «target_datastore»
usa el socket «target_datastore»
usa el socket «backend»
usa el socket «databases»
usa el socket «etcd»
usa el socket «backend»
usa el socket «backend»
usa el socket «cache»
usa el socket «state_store»
usa el socket «forward_target»
usa el socket «backend»
usa el socket «cache»
usa el socket «chunk_cache»
usa el socket «scrape_target»
usa el socket «backend»
usa el socket «backend»
usa el socket «database»
se aplica a
se aplica a
se aplica a
implementa
implementa
implementa