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).
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
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
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
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
Audit, AuditRequestHeader, RateLimitQuota, QuotaConfig, Plugin, CORSConfig, UIHeader, Logger and RaftAutopilot in a child namespace stop with RootOnlyKind
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)