Component
core/security/openbao
An OpenBao secrets-management server. OpenBao stores, generates, and controls access to tokens, passwords, certificates, and other secrets behind an authenticated HTTP API, and encrypts data at rest on a durable data volume — so it renders as a self-hosted, stateful running server, not a managed-cloud resource. Its operational type is therefore `stateful-server`: the deployment runs and owns the OpenBao process backed by a persistent volume. This component ships a single standalone server that keeps its state in the built-in file storage backend; highly-available, multi-node topologies are a future refinement not modelled here. OpenBao is initialized and unsealed at runtime inside the cluster — its root token and unseal keys are produced by the running server after it starts — so the component declares no credential slot and no secret is materialized at render time. Realized on Kubernetes through its Helm Recipe; it has no standalone local-container form, so no Compose Recipe is provided. Exports its API endpoint host and port to consumers via the uses topology. OpenBao is distributed under the MPL-2.0 license. With `values.metrics_enabled` true the Recipe turns on OpenBao's Prometheus telemetry and publishes its address as `metrics_endpoint`. A scrape presents an OpenBao token, best one whose policy grants read and list on sys/metrics and nothing else.
Procedencia
- Digest del contenido
- sha256:23c9c7fe8b974078b50334df9cd0a72089f9d6ae92c93cdc826439fb914da97b
- Publicado
- 2026-11-10T10:13:49Z
- 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:f52d92728e93277b7e4fe852e6a2a331e14030515000abd0daa2f7495b42cd2c
Referencia en esta versión
oci://hub.aggrega.ai/component/core/security/openbao:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| ui_enabled | boolean | true | no | Whether the OpenBao server serves its built-in web UI on the API endpoint. Leave on for interactive administration; set false to expose the HTTP API only. |
| metrics_enabled | boolean | false | no | Turns on OpenBao's own metrics, in the Prometheus format, at /v1/sys/metrics on the API port, and publishes their address as `metrics_endpoint`; while false that key is empty. Only an active server serves them, and only to a token whose policy grants read and list on sys/metrics. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| external_base_url | string | — | no | Externally reachable base URL of the secrets API, as assembled at the ingress tier — for example https://secrets.example.com. The server advertises this as its own API address: the address it hands a client to be redirected to, and the one its plugin backends are given as the server's own. Omitted, the Recipe advertises the server's pod address, which is reachable only from inside the cluster. |
| source_version | string | — | no | Source artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility. |
| 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 secrets API. A consumer points its client's address at this name together with `port`. |
| port | integer | — | sí | TCP port that Service accepts API requests on. The realization serves the project's own default, so a consumer reads this rather than hard-coding one. |
| protocol | string | — | no | How the published address is spoken to — `http`, the scheme a consumer composes its client address on. |
| metrics_endpoint | string | — | no | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:8200/v1/sys/metrics`, the host being the server's Service name. Empty while values.metrics_enabled is false. A scrape asks for the Prometheus format with the parameter format=prometheus. |
| metrics_credential_required | boolean | — | no | Whether a scrape of `metrics_endpoint` must present a credential: true while values.metrics_enabled is true, because OpenBao answers its metrics only to a token, and false while no address is published. Present a token whose policy grants read and list on sys/metrics and nothing else, so the scraper reads the metrics and no secret. |
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.
No se declararon slots de acoplamiento.
Lista de permitidos de autoinyección
No se declararon canales de autoinyección.
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 «auth_core»
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «backend»
usa el socket «databases»
usa el socket «etcd»
usa el socket «backend»
usa el socket «backend»
usa el socket «forward_target»
usa el socket «scrape_target»
usa el socket «backend»
usa el socket «jailbreak_detection»
usa el socket «database»
se aplica a
se aplica a
se aplica a
implementa