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

Recipe

openbao

OpenBao secrets-management server on Kubernetes via the official OpenBao Helm chart (openbao/openbao). The chart is configured for a lean, single-workload deployment: the agent injector is disabled, the server runs in standalone mode with a single replica, and its state is kept in the built-in file storage backend on a persistent volume. Under this configuration the chart renders a StatefulSet for the server, a ConfigMap carrying the server configuration, the main and internal (headless) Services, a ServiceAccount, a ClusterRoleBinding, and the chart's own test Pod, marked as a helm test hook. OpenBao is initialized and unsealed at runtime inside the cluster, so no credential is wired at render time and no secret is materialized. With `infra.external_base_url` set, the server advertises it as its API address through the chart's `server.ha.apiAddr`, which the chart reads in every mode; unset, the chart advertises the pod's own address. The server image is pinned to a resolvable release tag for reproducible renders. Default chart version in source.version; override via infra.source_version. provides.host is the bare, self-contained in-cluster Service name — 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). OpenBao is distributed under the MPL-2.0 license. With `values.metrics_enabled` true the server configuration gains a telemetry stanza turning on its Prometheus metrics, served at /v1/sys/metrics on the API port to a token, and provides.metrics_endpoint publishes the address; false writes nothing and leaves that key empty.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:f6f5f9283ae93920cc59bd8ead1a1decf1fa6c6b21ea6992949bc044f74d4f15
Publicado
2026-11-10T10:26:18Z
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:29d7143ca9efd977dd39e6f9f76ae94cfef1aea9af3b8e02d5a471ed43e56a16

Referencia en esta versión

oci://hub.aggrega.ai/recipe/helm/openbao:1.0.0
Destino
—
Implementa
core/security/openbao:1.0.0

Proporciona

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

NombrePlantilla
host{{ .context.rendered_name }}
port8200
protocolhttp
metrics_endpoint{{ if .values.metrics_enabled }}http://{{ .context.rendered_name }}:8200/v1/sys/metrics{{ end }}
metrics_credential_required{{ if .values.metrics_enabled }}true{{ else }}false{{ end }}

Workload

No se declaró ninguna plantilla de carga de trabajo.

Variables locales

No se declararon variables locales.

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/security/openbao: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