Compatibility Matrix

Use the compatibility matrix when you need the exact validation and support boundary for a platform or version.

This page is the contract for what the project actively validates, what remains best-effort supported, and what should be treated as out of scope for the current pre-GA line. It is the fastest way to answer whether a target Kubernetes or OpenBao version sits inside the tested envelope.

Terminology

Use these terms consistently on this page:

• Validated: explicitly exercised in CI.
• Best-effort supported: eligible for issue triage and fixes on the latest stable release line only.
• Recommended for production: stable releases using the documented Hardened profile, selfInit, admission enforcement, explicit version pinning, and staged upgrade validation.

Pre-GA posture

The current stable release line is intended for real deployments, but it remains pre-GA. The served CRD API is openbao.org/v1alpha1, and minor releases may introduce breaking changes. See Deprecation Policy and Support Policy for the full release contract.

Reference table

Kubernetes versions

Kubernetes versions.

Version	Validated	Support posture	Production note
v1.35	PR gate plus nightly E2E	Best-effort supported on the latest stable line	Primary validated baseline
v1.34	Nightly E2E	Best-effort supported on the latest stable line	Recommended after staging validation
v1.33	Nightly E2E	Best-effort supported on the latest stable line	Minimum validated version
v1.32	Not validated	Out of support scope	Do not use for the current pre-GA line

Reference table

Platforms

Platforms.

Platform	Validated	Support posture	Production note
Kubernetes	Default CI and nightly path	Best-effort supported on the latest stable line	Default recommended platform path
OpenShift	Helm rendering regression checks, manifest admission tests, and focused platform E2E	Best-effort supported on the latest stable line	Validate on your target cluster before production rollout

Reference table

OpenBao versions

OpenBao versions.

Version	Validated	Support posture	Production note
2.5.x	PR gate, nightly E2E, and config compatibility checks	Best-effort supported on the latest stable line	Primary validated target
2.4.x	Nightly config compatibility checks	Best-effort supported on the latest stable line	Validate workload behavior and upgrade flow in staging before production rollout
2.3.x	Not validated	Deprecated and out of support scope	Upgrade before production use

Reference table

CI validation matrix

Treat the CI configuration as the source of truth for what is actually exercised.

CI validation matrix. Treat the CI configuration as the source of truth for what is actually exercised.

Workflow	Scope	Versions tested
PR Gate	Logic, manifests, and primary compatibility path	K8s 1.35 + OpenBao 2.5.0
Nightly E2E	Full lifecycle coverage	K8s 1.33, 1.34, 1.35 + OpenBao 2.5.0
Nightly Config Compatibility	Render and config compatibility checks	OpenBao 2.4.4 and 2.5.0

Production upgrade rule

Always validate new Kubernetes or OpenBao versions in a staging environment before upgrading production, even when they are listed as validated and best-effort supported.

Related reference pages

Upgrade compatibilityUse the exact upgrade-path contract when the next question is sequencing rather than version support.Support policyOpen the support contract when you need to know what the project maintains beyond raw validation coverage.Known limitationsCheck current caveats and non-goals before assuming that an unvalidated path is only temporarily undocumented.