Esta página se tradujo automáticamente. Leer el original en inglés.

Recipe

cognee

A semantic-memory store on Kubernetes via the helm provider's Workload synthesis, running the official upstream image directly (no external Helm chart). The graph, the embeddings and the bookkeeping tables all live in files under one persistent volume, so the workload renders as a StatefulSet with that volume mounted at the state root, alongside the governing headless Service the stateful form requires and a ClusterIP Service publishing the API port. This realization is where the component's engine value is earned: the container's configuration names the graph engine the entities and relations are written into, the store the embeddings are written into, the models the ingested material is read and encoded with, and the ontology the extracted names are resolved against — so the rendered artifact shows how memory is built rather than leaving it to the running process to reveal. A store that only indexed vectors would carry none of those settings. A credential attached on a model connection reaches the server as an env secretKeyRef — LLM_API_KEY for the extraction model, EMBEDDING_API_KEY for the embedding model — so its value never appears in the rendered manifest; the component's model_api_key is read only for a socket left unwired, under the same names. With nothing attached, the server holds no model credential. provides.host is the bare, self-contained in-cluster service name of the synthesized ClusterIP Service — it carries no namespace, so the recipe is independent of where it is deployed. A consumer in another namespace qualifies the host with the target namespace on its own side (caller-side routing). The configuration contract is authored against cognee 1.5.3.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:4e4531ebfca0924059ddfde24084d143d2fc2917bb45d31c7a8ab6161195ce46
Publicado
2026-11-10T10:22:48Z
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:940c4fa0e663a5e2d3f1f0756d1efc2e4a4610cf9c9c943454d6dc6c0e052947

Referencia en esta versión

oci://hub.aggrega.ai/recipe/helm/cognee:1.0.0
Destino
—
Implementa
core/datastore/cognee:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

NombrePlantilla
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
endpointhttp://{{ .context.rendered_name }}-default:{{ .infra.port }}
protocolhttp

Workload

Workload · form: stateful · replicas: 1 · containers: main

Variables locales

NombrePlantilla
state_root/var/lib/cognee

Mapeo de valores

No se declaró ningún mapeo de valores.

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

  • implementaimplementacontrato compatible

    core/datastore/cognee:1.0.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad