mirror of https://github.com/hashicorp/boundary
docs: Release notes 07-31 (#4978)
* docs: Release notes 07-31 * docs: Updates based on feedbackpull/4985/head
Dan Heath
2 years ago
committed by
GitHub
parent
bbbe971ed1
commit
7ebc851f56
@ -0,0 +1,129 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.17.0
|
||||
description: |-
|
||||
Boundary release notes for v0.17.0
|
||||
---
|
||||
|
||||
# Boundary 0.17.0 release notes
|
||||
|
||||
**GA date:** July 31, 2024
|
||||
|
||||
@include 'release-notes/intro.mdx'
|
||||
|
||||
## New features
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th style={{verticalAlign: 'middle'}}>Feature</th>
|
||||
<th style={{verticalAlign: 'middle'}}>Update</th>
|
||||
<th style={{verticalAlign: 'middle'}}>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
<tr>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
Centralized tag management for workers
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
GA
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
Prior to this version, if you wanted to edit or update worker tags, you had to do it using the worker configuration file, the CLI, or the API. Now, you can edit worker tags directly in the Boundary UI.
|
||||
<br /><br />
|
||||
Learn more: <a href="/boundary/docs/concepts/filtering/worker-tags">Worker tags</a>.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
Multi-scope roles and inheritance
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
GA
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
You can now assign a single role to multiple scopes, making it easier to grant permissions to users who must access resources across multiple scopes. You can also configure children scopes to inherit roles.
|
||||
<br /><br />
|
||||
Learn more: <a href="/boundary/docs/concepts/security/permissions">Permissions in Boundary</a>.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
Improved worker failure handling
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
GA
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
When you attempt to connect to a target, Boundary randomly selects a worker that has the matching tags to proxy the connection. Before release 0.17.0, unhealthy workers that had issues related to the external storage provider were eligible to proxy connections. The connections would fail, and users had to restart the connection until Boundary selected a healthy worker. <br /><br />
|
||||
In this release, Boundary removes workers from the pool of available workers if they have issues with the external storage provider for improved worker failure handling.
|
||||
<br /><br />
|
||||
Learn more: <a href="/boundary/docs/configuration/session-recording/configure-worker-storage">Configure workers for session recording</a>.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
S3-compliant storage options for session recording
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
GA
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
As of Boundary 0.16.0, the MinIO plugin made it possible to use MinIO storage as a storage option for session recording. Starting in this release, you can use the MinIO plugin to configure storage using other S3-compliant storage providers.
|
||||
<br /><br />
|
||||
Learn more: <a href="/boundary/docs/configuration/session-recording/storage-providers/configure-s3-compliant">Configure S3-compliant storage for session recording</a>.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Known issues and breaking changes
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th style={{verticalAlign: 'middle'}}>Version</th>
|
||||
<th style={{verticalAlign: 'middle'}}>Issue</th>
|
||||
<th style={{verticalAligh: 'middle'}}>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
<tr>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
0.13.0+
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
Rotation of AWS access and secret keys during a session results in stale recordings
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
In Boundary version 0.13.0+, when you rotate a storage bucket's secrets, any new sessions use the new credentials. However, previously established sessions continue to use the old credentials.
|
||||
<br /><br />
|
||||
As a best practice, administrators should rotate credentials in a phased manner, ensuring that all previously established sessions are completed before revoking the stale credentials.
|
||||
Otherwise, you may end up with recordings that aren't stored in the remote storage bucket, and are unable to be played back.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
0.13.0+
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
Unsupported recovery workflow during worker failure
|
||||
</td>
|
||||
<td style={{verticalAlign: 'middle'}}>
|
||||
If a worker fails during a recording, there is no way to recover the recording. This could happen due to a network connectivity issue or because a worker is scaled down, for example.
|
||||
<br /><br />
|
||||
Learn more:
|
||||
<a href="/boundary/docs/troubleshoot/troubleshoot-recorded-sessions#unsupported-recovery-workflow">Unsupported recovery workflow</a>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
Loading…
Reference in new issue