Skip to content

Guides

Each guide reaches one goal with the operator. They assume an installed operator and a Ready connection (Install, Connect to OpenBao).

The manifests come from examples/, where CI checks every file against the CRDs. They use the Kubernetes namespace openbao-config and a connection named openbao; change both to yours. Values such as passwords, keys and certificates in them are fake placeholders. The check steps read OpenBao with the bao CLI, so set BAO_ADDR and a token that may read the paths.

To learn the operator step by step on a test cluster first, follow the tutorials.

Start with a configuration task

Task Guide Result to verify
Deliver configuration from Git Argo CD, Flux Delivery waits until the operator reports the configuration ready
Declare an ACL policy Manage policies The resource is Ready and bao policy read returns its HCL
Give a workload access Kubernetes authentication Its ServiceAccount can log in with the intended audience and policy
Adopt existing configuration Import, then migration Observe reports the intended state before you enable management
Check the tenant boundary Security model Connections use scoped identities and tenant policies limit managed paths

Authentication

  • Kubernetes auth


    Let workloads log in with their ServiceAccount token.

  • JWT and OIDC auth


    Browser logins through an identity provider, and CI jobs with their job JWT.

  • AppRole


    Machine logins outside Kubernetes, with secret IDs the operator rotates.

Secrets engines

  • KV secrets


    KV version 2 mounts, secrets from Kubernetes Secrets, and generated values.

  • Database secrets


    Dynamic and static database credentials.

  • PKI


    A root and an intermediate CA, and a role that issues certificates.

  • Transit


    Encryption keys with scheduled rotation.

Identity and access

  • Identity


    Entities, groups, aliases, and OpenBao as an OIDC provider.

  • Access model


    Grant KV access to ServiceAccounts and to identity provider groups without writing policies.

  • Templated policies


    One policy that gives every workload its own path.

  • Namespaces and tenants


    One OpenBao namespace and one connection per team.

Adopt and deliver