Component
core/datastore/valkey
A Valkey in-memory key-value cache, speaking the Redis wire protocol. Used as a cache, entries live in memory and are not durably persisted, so the component renders as a stateless workload rather than a stateful one and declares no storage. Realized on Kubernetes, on Compose for local development, on Amazon ElastiCache and on Google Cloud Memorystore for Valkey. Exports its host and port to consumers via the uses topology. On Kubernetes there are two realizations and the Manifest chooses between them. `valkey` synthesizes the cache as a workload and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `valkey-chart` renders the community-maintained Valkey Helm chart, which hardens the container further, so reach for it where a chart repository is reachable at build time. Reach for terraform/valkey-elasticache, or cloudformation/valkey-elasticache in a CloudFormation stack, where the cache is an ElastiCache service in the operator's AWS account; each halts naming each value ElastiCache cannot apply. Reach for terraform/valkey-memorystore where it is a Memorystore instance in the operator's Google Cloud project, whose VPC network has a service connection policy for Memorystore; it runs without authentication. `infra.client_tls`, off by default, serves TLS alone and publishes `protocol` `valkey-tls`: on Kubernetes with the certificate attached to `server_certificate`, on ElastiCache with one AWS issues, on Memorystore with one from the instance's own authority, which consumers trust through `server_ca`. The Compose realization refuses it by name.
Procedencia
- Digest del contenido
- sha256:627bb5b54ca1ad5133cd336470135b3603a2965b15f62119068aabe4a705bb07
- Publicado
- 2026-11-10T10:11:19Z
- 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:4867028e2f070a500d3f8f8e0b017f93b3c203b85738a9e55052969d350431c9
Referencia en esta versión
oci://hub.aggrega.ai/component/core/datastore/valkey:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| maxmemory | string | — | no | Maximum memory the cache may use before eviction (the maxmemory directive, e.g. 256mb). Omit for no cap. ElastiCache fixes it by the node type, so its realizations halt on it; Memorystore takes it as a configuration, except on the SHARED_CORE_NANO node type. |
| maxmemory_policy | string | — | no | Eviction policy applied when maxmemory is reached (the maxmemory-policy directive, e.g. allkeys-lru, volatile-ttl, noeviction). Omit to use the default. |
| databases | integer (min 1) | — | no | Number of logical databases (the databases directive). Omit to use the default (16). |
| appendonly | boolean | false | no | Enable append-only file (AOF) persistence. Pair with persistence.enabled for a durable volume; on an ephemeral cache the AOF is not retained across restarts. ElastiCache writes no AOF for Valkey, so its realizations halt on it set true; Memorystore keeps the data with AOF persistence. |
| persistence | object | — | no | — |
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) | 6379 | no | Server listen port. Most operators should omit this and let the Recipe assign the default (6379). Memorystore serves 6379 alone, so terraform/valkey-memorystore halts on any other value. |
| client_tls | boolean | false | no | Serve client connections over TLS alone. Off by default, which serves plaintext and renders exactly as a cache without the setting. On, the server listens for TLS on `port` with no plaintext listener, presents the certificate attached to `server_certificate` (required while this is on), requests no client certificate, and the published `protocol` is `valkey-tls`. Served by the `valkey` and `valkey-chart` Kubernetes realizations; the Compose realization refuses it. On ElastiCache it turns on the service's in-transit encryption, whose certificate AWS issues and clients trust without a `server_ca`. On Memorystore it turns on the service's in-transit encryption with the instance's own certificate authority, which each consumer takes in its `server_ca` slot. |
| engine_version | string | 8.1-alpine | no | Valkey container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag. The ElastiCache realizations read the major and minor version the value begins with (8.1 from 8.1-alpine) as the engine version, and halt on one ElastiCache does not offer, naming those it does. terraform/valkey-memorystore reads it the same way and takes 7.2, 8.0, 9.0 and 9.1, so the default halts there and the Release sets one of them. |
| 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, and the ElastiCache and Memorystore realizations ignore it too, the terraform ElastiCache one pinning the module it vendors at a version it writes out, the Memorystore one vendoring a module kept beside it and the CloudFormation one pulling nothing. 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í | Address a consumer opens its cache connection to, together with `port`: the in-cluster DNS name of the Service fronting the cache on Kubernetes, and on ElastiCache or Memorystore a pointer string Terraform or CloudFormation resolves to the primary endpoint, or the DNS name the Release sets in infra.overrides.host instead, so a consumer on another target receives an address it can resolve. |
| port | integer | — | sí | TCP port the cache accepts connections on. It follows the port an operator set in the Release, or the one port the service serves on Memorystore, so a consumer reads it rather than assuming 6379. |
| protocol | string | — | no | Wire protocol the published address speaks — `valkey`, naming the server on the other end, while `infra.client_tls` is off, and `valkey-tls` while it is on, when the address accepts TLS connections alone. A consumer reaches either with a Redis-protocol client, over TLS for `valkey-tls`. A client that reads only `host` and `port` reads this key too to learn that TLS is required: a plaintext client reaching a TLS listener fails its handshake and exchanges no command. |
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 |
|---|---|---|---|---|---|
| password | feature.aggrega.ai/kind=secret | no | env | sí | Optional cache authentication credential. When attached, enables Valkey password authentication and supplies the password; unattached, the cache runs without authentication. On ElastiCache the password is the AUTH token, which the service accepts only while infra.client_tls is true, drawn by core/random-password, when Terraform applies or the stack is created, with no punctuation and at least 16 characters. Memorystore for Valkey takes no password a Release supplies, so terraform/valkey-memorystore halts on any attachment here. |
| server_certificate | feature.aggrega.ai/kind=secret | no | file | sí | Optional certificate the cache presents to its clients while infra.client_tls is true: a Secret holding tls.crt, the certificate followed by any intermediate certificates, and tls.key, its private key, the two keys a kubernetes.io/tls Secret holds. The certificate names every address a client dials: the published host, and its namespace-qualified forms where clients in other namespaces connect. Mounted as files, so attach a Feature that names an existing Secret, such as core/referenced-secret. Required by the Kubernetes realizations while client_tls is true; a build halts on it attached while client_tls is false. ElastiCache presents a certificate AWS issues, and Memorystore one from the instance's own authority, so their realizations halt on any attachment here. |
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 «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «backend»
usa el socket «cache»
usa el socket «state_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 «storage»
usa el socket «metadata_store»
usa el socket «target_datastore»
usa el socket «cache_store»
usa el socket «cache»
usa el socket «cache»
usa el socket «cache_store»
usa el socket «upstream»
usa el socket «cache»
usa el socket «cache_store»
usa el socket «cache»
usa el socket «state_store»
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 «store»
usa el socket «backend»
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
implementa
implementa
implementa
implementa
implementa
implementa