Support Considerations for Self-Managed Workers

HCP Boundary environments function optimally when workers and controllers are running the same version. The following section outlines API compatibility and hot-fix policies for self-managed workers in HCP Boundary environments.

Controller and worker API compatibility

HCP Boundary only supports API backwards compatibility between HCP Boundary and self-managed workers from the prior “major release”. A major release is identified by a change in the first (X) or second (Y) digit in the following versioning nomenclature: Version X.Y.Z. All self-managed workers within an environment must be on the same version.

For example, Boundary self-managed workers version 0.11.0 are compatible with HCP Boundary environments running Boundary 0.12.0. However, they will not have compatibility once the HCP Boundary control plane is updated to version 0.13.0 or above.

Security and other bug fixes

Eligible code-fixes and hot-fixes for HCP Boundary self-managed workers are only provided via a new minor release (Z) on top of the latest “major release” branch.

Shared responsibilities

HashiCorp is responsible for keeping the customers’ HCP Boundary control plane versions up to date with the latest release of Boundary software. Customers are expected to maintain their self-managed workers and ensure that they are running the same version as the control plane. It is important to note that all self-managed workers must be on the same major and minor version, without any exceptions.