Skip to content

Known limitations

Limitations of the current release that affect users, with the workaround where one exists. The sources are the tech-debt register, the backlog, the ADRs and the architecture; each entry links to its source. An entry leaves this page when its source is closed.

Alpha API

All CRDs are v1alpha1: a minor release may change them, following the deprecation policy. The API group domain openbaoconfig.io is final (ADR 0008).

Verification

limitation effect source
Integration tests use bao server -dev: in-memory storage, a root token, one node, no TLS storage, HA, TLS and least-privilege behaviour of a production server are not exercised by the per-kind tests. The e2e test in kind adds a tenant login under a non-root policy for three kinds TD-001
Only OpenBao 2.7.2 runs in CI; 2.6 is covered by its OpenAPI snapshot a behaviour difference on 2.6 is not caught BL-014, compatibility
Field-level API coverage is not checked a request field added or renamed upstream on a typed path is noticed only by hand; use OpenBaoEndpoint for it meanwhile TD-003
External-plugin kinds are not run against a server they are verified by golden payload tests only, and paths marked (u) in the kind catalogue come from documentation, not OpenBao source; they are disabled by default TD-004
The default conformance test and the full no-write run over every kind run on pushes to main, weekly and on demand; a pull request runs the no-write test only for the kinds it touches, every kind of a group whose Go code changes, or every kind when shared code changes a change that breaks the default test of a kind can merge and is caught afterwards architecture

Drift detection and comparison

limitation effect source
No test checks that each kind's Desired covers every field of its CRD schema a field an adapter leaves out of its payload is not compared, so removing it from the spec does not unset it in OpenBao; set the field to its default explicitly BL-012, architecture
Some fields cannot return to their default once set, such as a pinned mount plugin_version or a PKI default issuer OpenBao keeps the stored value when the field is removed from the spec test/conformance/exceptions.yaml, architecture
OpenBaoEndpoint compares only its data keys a key removed from data is not unset on the server architecture
Write-only fields cannot be compared drift in a password or other value OpenBao does not return is invisible; the operator writes it again only when the input Secret or spec changes architecture
The read after a write is not pinned to the active node on a cluster whose standbys serve reads, a read-back can return stale values and report OutOfSync, retried with backoff architecture
Drift reads always go to the configured address reading from standbys (horizontal read scaling) is planned architecture
The write budget is one window per OpenBaoServer, shared by every namespace one namespace whose objects keep drifting can delay other namespaces' drift repairs on the same server BL-016

Ownership and restore

limitation effect source
Only entities, groups and namespaces carry a server-side ownership marker after status loss, other kinds need a one-time creationPolicy: Adopt to be managed again ADR 0012
GroupMembership, AccessGrant and AccessLayout keep the members and children they own only in status a restore without status cannot remove members or children that the spec no longer lists; remove them by hand BL-011, backup and restore
Creates are serialised per process with several replicas, leader election must stay on (the chart default) architecture
The hash key of status.writeOnlyHash cannot be rotated without rewriting every write-only field if the hash-key Secret is deleted, the next manager start creates a new key and every object with write-only inputs is rewritten once architecture, roadmap

OpenBao behaviour

limitation effect workaround source
A standby that serves requests itself (the OpenBao 2.7 default) answers failed to update audit table (400) to an audit enable and does not forward it Audit reports ReconcileError point the OpenBaoServer address at the active node only, or set disable_standby_reads = true in the OpenBao server configuration troubleshooting
A proxy or a standby without request forwarding answers with a redirect the operator never follows redirects: resource ReconcileError, connection AuthenticationFailed point the address at the active node or a service that forwards troubleshooting
Nine sys kinds exist only in the root namespace Audit, AuditRequestHeader, RateLimitQuota, QuotaConfig, Plugin, CORSConfig, UIHeader, Logger and RaftAutopilot in a child namespace stop with RootOnlyKind use a connection based in the root namespace architecture
KeyRotationConfig needs the root or a sealable namespace Unsupported elsewhere architecture
A KV version 2 history purge cannot be conditional bounded version destruction preserves later writes but cannot distinguish metadata deleted and recreated concurrently do not delete/recreate metadata while cleanup is pending TD-008

Kinds and features

limitation effect source
External-plugin kinds are disabled by default enable them with pluginKinds.enabled; each reports Unsupported until its plugin is registered and mounted kind catalogue, BL-005
No typed kind yet for CertAuthCRL, TransitCacheConfig and KV version 2 metadata use OpenBaoEndpoint BL-009
No kind for features OpenBao does not have (Sentinel, KMIP, Transform, managed keys, replication) or for one-off actions (a login, a PKI sign, creating a token) out of scope architecture
DatabaseConnection.pluginConfig.connection_url is not checked for a literal password connectionURL refuses one; the same value in pluginConfig is accepted. BL-017
Namespace sealing on OpenBaoNamespace is planned not available architecture
Plugin support end to end (roadmap phase 5) is planned registering a plugin and mounting it through pluginRef is not verified against a server with the plugin in CI architecture

Security and install

limitation effect workaround source
The default install can read Secrets and ConfigMaps and request ServiceAccount tokens cluster-wide the tenant boundary relies on each connection's OpenBao identity, not on Kubernetes RBAC set watchNamespaces for a Role per namespace TD-005
One-time outputs (secret IDs, client secrets, generated keys) live in Kubernetes Secrets etcd encryption and RBAC protect them, not OpenBao architecture
The NetworkPolicy is on by default but leaves egress open by destination while apiServer.cidrs and openbao.to are empty the operator can reach any host on the API server and OpenBao ports name the peers hardening
The documentation site is built with Material for MkDocs, which reaches end of life on 2027-05-05 no user effect today TD-006