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.
Herkunft
- Inhalts-Digest
- sha256:23c9c7fe8b974078b50334df9cd0a72089f9d6ae92c93cdc826439fb914da97b
- Veröffentlicht
- 2026-11-10T10:13:49Z
- Signaturidentität
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signatur
- Offiziellapplication/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
Referenz zu dieser Version
oci://hub.aggrega.ai/component/core/security/openbao:1.0.0Entwicklerparameter
Werte, die der Entwickler im Aggregate festlegt.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| ui_enabled | boolean | true | nein | 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 | nein | 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. |
Dimensionierung durch den Operator
Infrastrukturdimensionierung, die der Operator pro Umgebung anpasst.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| external_base_url | string | — | nein | 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 | — | nein | Source artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility. |
| compute | object | — | nein | — |
| storage | object | — | nein | — |
| overrides | object (open) | — | nein | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Ausgabevertrag
Werte, die diese Komponente über die uses-Topologie an Konsumenten veröffentlicht.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| host | string | — | ja | 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 | — | ja | 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 | — | nein | How the published address is spoken to — `http`, the scheme a consumer composes its client address on. |
| metrics_endpoint | string | — | nein | 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 | — | nein | 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. |
uses-Sockets
Die Abhängigkeits-Sockets, über die sich diese Komponente verbindet. Das Ziel jeder über einen Socket verdrahteten Verbindung muss dessen Label-Selektor erfüllen, und jede Verbindung kann in den Slots, die der Socket deklariert, eine Anbindung tragen. Einen erforderlichen Slot muss jede Verbindung füllen, die das Aggregate oder das Release über den Socket verdrahtet.
Keine uses-Sockets deklariert.
Anbindungs-Slots
Benannte Bindungspunkte, an denen ein Feature an diese Komponente angebunden wird. Der Selektor eines Slots schränkt ein, welches Feature ihn füllen darf, und seine inject-Liste benennt, wie das Feature sein Material liefern darf. Ein erforderlicher Slot muss auf jeder Instanz gebunden sein, durch eine Anbindung an der Instanz oder in einem darüberliegenden Geltungsbereich, und ein sensibler Slot ist für den Umgang mit geheimem Material deklariert. Ein Feature kann auch unter einem Namen angebunden werden, den kein Slot deklariert.
Keine Anbindungs-Slots deklariert.
Zulassungsliste für Selbstinjektion
Keine Selbstinjektions-Pipes deklariert.
Beziehungen
Typisierte Kanten zu und von anderen veröffentlichten Entitäten. Eine Referenz ohne veröffentlichtes Ziel wird als unterbrochene Kante statt als Link dargestellt.
Verwendet
Diese Entität verwendet nichts aus dem Katalog.
Verwendet von
verwendet Socket «auth_core»
verwendet Socket «auth_core»
verwendet Socket «auth_core»
verwendet Socket «auth_core»
verwendet Socket «backend»
verwendet Socket «databases»
verwendet Socket «etcd»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «forward_target»
verwendet Socket «scrape_target»
verwendet Socket «backend»
verwendet Socket «jailbreak_detection»
verwendet Socket «database»
gilt für
gilt für
gilt für
implementiert