CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Add max # of connections to known issues (#4405)

Browse Source
This commit is contained in:
Dan Heath authored and GitHub committed 2024-02-13 17:47:59 -05:00
1 parent c72c614200
commit 2b938a8f10
1 file changed
+19
Download Patch File Download Diff File Expand all files Collapse all files
website/content/docs/release-notes/v0_15_0.mdx
+19
View File
@@ -178,6 +178,25 @@ description: |-
</td>
</tr>
<tr>
<td style={{verticalAlign: 'middle'}}>
0.15.0
</td>
<td style={{verticalAlign: 'middle'}}>
Maximum number of connections allowed is incorrect
</td>
<td style={{verticalAlign: 'middle'}}>
A known issue causes Boundary to permit one less than the allowed number of connections that you configured for a given target. For example, if you configured the session connection limit for a target at 2, Boundary only permits 1 connection to the target. If the value is 1, Boundary does not allow any connections to the target.
<br /><br />
This is a known issue that will be fixed in an upcoming release. A value of -1 still means that connections to the target are unlimited.
<br /><br />
Learn more:&nbsp;
Refer to the CLI docs for information about using <a href="/boundary/docs/commands/targets/create"><code>targets create</code></a> or <a href="/boundary/docs/commands/targets/update"><code>targets update</code></a> to configure a maximum number of connections.
<br /><br />
Refer to the API docs for information about using <a href="/boundary/api-docs/target-service">Target service</a> to configure a maximum number of connections.
</td>
</tr>
</tbody>
</table>