The operator keeps the configuration of an existing OpenBao server in the state Kubernetes custom
resources declare. Each record states its status, the context that forced the choice, the decision
and the consequences.
Every OpenBao call uses github.com/openbao/openbao/api/v2 through a small logical client, and adapters call generic paths instead of the typed Sys() helpers.
The desired payload includes every typed field, an omitted field is sent as the default the adapter declares, and OpenBaoEndpoint still compares only its own data keys.
Access-critical kinds are re-read every 15 minutes and other kinds every hour, with jitter, and a spec change is served ahead of drift reads under that server's rate limit.
A namespaced connection logs in as a ServiceAccount in its own namespace, never as the operator, and a cluster-scoped connection is limited to the namespaces it allows.
The platform-owned OpenBaoServer holds the address, CA bundle, allowed namespaces, audiences, rate limit and request timeout, and a connection names that server and carries no address of its own.
Mounts, namespaces, KV and random secrets, audit devices, key material, MFA methods, entities and OpenBaoEndpoint delete only with openbaoconfig.io/allow-destructive-delete: "true", and a terminating Kubernetes namespace orphans them.
Rewrites of an owned object whose spec and input secrets are unchanged are capped at 60 per minute per server; creates, adoptions, spec changes and new secret inputs do not spend that budget.
openbaoconfig.io/paused: "true" on a resource, its Kubernetes namespace or its OpenBaoServer stops reads, writes and deletes, and a deletion keeps the finalizer.
OpenBaoEndpoint writes any payload to any path through the same engine, and deletionPolicy: Delete also requires openbaoconfig.io/allow-destructive-delete: "true".
A new CRD version only adds fields, Kubernetes converts it with conversion: None, and a conversion webhook is reserved for a break that cannot be avoided.
Adapters absorb OpenBao's wire changes, and a CRD changes only when users gain a field or lose one that OpenBao removed, so an OpenBao release does not bump the CRD version.