Component
core/datastore/milvus
A Milvus vector database. Stores embedding vectors with their scalar fields and answers similarity searches over them, so a component that retrieves by similarity is wired here. Collections are created through Milvus's own API at runtime; the component declares the server, not its contents. It runs as one standalone server holding its metadata store and its data on one volume, with no separate etcd or object store to deploy. Exports its host, port, protocol, an endpoint joining them and the account a client signs in as. Authentication is off unless a password is attached; attached, it is switched on for the API and for the management endpoints the metrics port serves, whose health check and metrics stay open, and the password is delivered by reference. Realized by the product's own Helm chart on Kubernetes, fetched at build time, and by a Compose Recipe for local development. Its Recipes are verified by their rendered output, not by a started server.
Provenance
- Content digest
- sha256:25705f2b7f93c21a738c2b5aafb19cfc4e58971651ad3b600cdc8a73a2f679a9
- Published
- 2026-11-10T10:10:52Z
- 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:e30d85006e21928f7c4a1b44a69cab366aa1d2957fba9381e048c07ae58a9e3d
Reference at this version
oci://hub.aggrega.ai/component/core/datastore/milvus:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| custom_config | string | — | no | Raw server configuration block (milvus.yaml format), delivered to the server as its user.yaml, which it reads over its built-in settings, so a setting the block omits keeps its default. The settings the Recipes make themselves take precedence over the block: the listen port, the embedded metadata store and local storage, and authentication, which follows the password slot alone. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 19530 | no | Port the server's API is published on — the gRPC API and the RESTful API share it. Most operators should omit this and let the Recipe assign the default (19530). On Kubernetes it is the Service port, forwarding to the port the chart's container listens on; on Compose the server listens on it. |
| engine_version | string | v3.0.3@sha256:08747249b27c64f158db79a53ba008f89314ee240c731e585a7ec4fb7140731e | no | Tag of the milvusdb/milvus image every Recipe runs, optionally followed by @ and the digest it must resolve to. The Recipes configure the server through the settings of the 3.0 release; another release may need other ones. |
| source_version | string | — | no | Version of the Helm chart the Kubernetes Recipe pulls. Read only by that Recipe; the Compose Recipe pulls no source artifact and ignores 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. |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | Address a client connects to. On Kubernetes it is the Service's DNS name, and on Compose the service name. |
| port | integer | — | yes | TCP port the server's API answers on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming 19530. |
| user | string | — | no | Name of the account a client signs in as when a password is attached — `root`, the account the server creates at its first start. The matching password arrives through the credential attached to the component, never through this contract. With no password attached the server checks no credential. |
| protocol | string | — | no | Scheme a client composes the server's address with — `http`, as in http://<host>:<port>, the form Milvus's own clients take. |
| endpoint | string | — | no | The server's address as one URI, http://<host>:<port>, for a client that takes one address rather than its parts. It carries no credential. |
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.
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| password | feature.aggrega.ai/kind=secret | no | env | yes | Optional password of the server's root account. When attached, authentication is switched on for the API and for the management endpoints on the metrics port, and the password is delivered by reference; unattached, authentication is off on both and the server accepts unauthenticated requests. |
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
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «knowledge_base»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «vector_store»
uses socket «vector_store»
uses socket «task_memory»
uses socket «document_store»
uses socket «vector_store»
uses socket «vector_store»
uses socket «checkpointer_db»
uses socket «checkpointer_db»
uses socket «backend»
uses socket «backend»
uses socket «backend»
uses socket «vector_store»
uses socket «vector_store»
uses socket «storage»
uses socket «knowledge_base»
uses socket «data_store»
uses socket «metadata_store»
uses socket «target_datastore»
uses socket «target_datastore»
uses socket «target_datastore»
uses socket «backend»
uses socket «databases»
uses socket «etcd»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «forward_target»
uses socket «backend»
uses socket «cache»
uses socket «chunk_cache»
uses socket «scrape_target»
uses socket «backend»
uses socket «backend»
uses socket «database»
applies to
applies to
applies to
implements
implements