Robert Main
18f469105c
* Update website folder to indicate deprecation Adds an alert banner to the top of all MDX files within `/website` to indicate deprecation * Update website README
43 lines
3.0 KiB
Plaintext
43 lines
3.0 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: v0.11.0 release notes
|
|
description: >-
|
|
Learn more about the features included in the Boundary 0.11.0 release and discover what has changed.
|
|
---
|
|
|
|
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to `web-unified-docs`, since changes to `/website` in this repository will not appear on developer.hashicorp.com.
|
|
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
|
|
|
|
# Boundary v0.11.0
|
|
|
|
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](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md). To learn about what Boundary
|
|
consists of, we highly recommend you start at the [Getting Started Page](/boundary/docs/getting-started).
|
|
|
|
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.11.0, please review Boundary's
|
|
[general upgrade guide](/boundary/tutorials/oss-configuration/upgrade-version).
|
|
|
|
## 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](/boundary/tutorials/access-management/hcp-vault-cred-brokering-quickstart).
|
|
|
|
**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](/boundary/tutorials/hcp-administration/hcp-ssh-cred-injection).
|
|
|
|
**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.
|
|
|
|
## What's changed
|
|
|
|
**For more detailed information of all changes since 0.10.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)** |