Esta página foi traduzida automaticamente. Ler o original em 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.

Proveniência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como editor oficial.
Digest do conteúdo
sha256:4e4531ebfca0924059ddfde24084d143d2fc2917bb45d31c7a8ab6161195ce46
Publicado
2026-11-10T10:22:48Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • 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

Referência nesta versão

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

Fornece

Modelos de ponteiros determinísticos que esta receita liga para os consumidores.

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

Workload

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

Variáveis locais

NomeModelo
state_root/var/lib/cognee

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é apresentada como uma aresta quebrada em vez de uma ligação.

Usa

  • implementaimplementacontrato compatível

    core/datastore/cognee:1.0.0

    Todas as saídas obrigatórias são satisfeitas e cada saída fornecida é nomeada no contrato.

Usado por

Nada no catálogo depende desta entidade.

Referência do conceito Recipe →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design partilhado do Aggrega.

Privacidade