From 6aa16992d5ffc709bb0ffdc934a4886c3087ce5d Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Mon, 29 Apr 2024 18:17:58 +0000 Subject: [PATCH] backport of commit ee8fad40adc52d3882af80c6bb1f65d50a980928 --- .../content/docs/release-notes/v0_16_0.mdx | 21 +++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/website/content/docs/release-notes/v0_16_0.mdx b/website/content/docs/release-notes/v0_16_0.mdx index 1a103448ae..ad2971d2f7 100644 --- a/website/content/docs/release-notes/v0_16_0.mdx +++ b/website/content/docs/release-notes/v0_16_0.mdx @@ -65,6 +65,20 @@ description: |- + + + Local storage state health + + + GA + + + Storage state values have been created to monitor the health of any local workers used for session recording. Boundary monitors the worker's available disk space and compares it to the value you configured for recording capacity. If the worker does not have adequate storage, it cannot be used for session recording. +

+ Learn more: Local storage for session recording. + + + @@ -126,13 +140,8 @@ description: |- - kms worker method - + - As noted in the v0.13.0 release notes, the kms worker method has been removed. Since version 0.13.0, you have had to opt in to use the deprecated method. Now it is no longer available and Boundary uses the new kms mechanism. -

- Learn more:  - KMS worker configuration