The release notes below contain information about new functionality available in the Boundary v0.11.0 release. To see a granular record of when each item was merged into the Boundary project, please refer to the Changelog. To learn about what Boundary consists of, we highly recommend you start at the Getting Started Page.
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.11.0, please review Boundary's general upgrade guide.
Boundary v0.11.0 Highlights
HCP Boundary General Availability: Boundary is now available on the HashiCorp Cloud Platform! HCP Boundary provides an easy way to securely access critical systems with fine-grained authorizations based on trusted identities. Boundary on HashiCorp Cloud Platform provides a fully managed, single workflow to securely connect to hosts and critical systems across Kubernetes clusters, cloud service catalogs, and on-premises infrastructure
Private Vault Access: HCP Boundary users are now able to integrate their on-premises instance of Vault without having to publicly expose Vault. This is accomplished by deploying a Boundary worker binary within the same private network as the Vault instance and peering with the HCP Boundary control plane. Learn more here.
SSH Credential Injection: SSH Targets can now be set up through the Admin UI, making the Credential Injection workflow more seamless and easy to use. Learn more here.
Improved Worker Management: Administrators are now able to register and manage Boundary workers through the Admin UI. Admin users can view session counts, IP addresses and release versions of all registered workers through the 'Workers' tab.
Support for Generic Credentials: Boundary now supports brokering of 'generic credentials'. This will enable users to broker any kind of key/value pair type credentials when they are connecting to a remote host.
For more detailed information of all changes since 0.10.0, please refer to the Changelog