chore: add release notes for workspace slot caps

[salonig23]

Ticket

Description

Test Plan

Checklist

• Changes have been manually QA'd
• New features have been approved by the corresponding PM
• User-facing API changes have the "User-facing API Change" label
• Release notes have been added as a separate file under docs/release-notes/
  See Release Note for details.
• Licenses have been included for new code which was copied and/or modified from any external code

[netlify]

✅ Deploy Preview for determined-ui canceled.

Name	Link
🔨 Latest commit	ad9ee55
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/66a15c87f653de000835d19e

[codecov]

Codecov Report

Attention: Patch coverage is 40.76016% with 904 lines in your changes missing coverage. Please review.

Project coverage is 53.36%. Comparing base (3995b72) to head (3f9dfd1).
Report is 4 commits behind head on main.

❗ Current head 3f9dfd1 differs from pull request most recent head ad9ee55

Please upload reports for the commit ad9ee55 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9706      +/-   ##
==========================================
- Coverage   53.55%   53.36%   -0.20%     
==========================================
  Files        1255     1255              
  Lines      152867   154035    +1168     
  Branches     3298     3293       -5     
==========================================
+ Hits        81865    82197     +332     
- Misses      70852    71688     +836     
  Partials      150      150              

Flag	Coverage Δ
backend	44.56% <47.48%> (-0.21%)	⬇️
harness	72.69% <7.35%> (-0.15%)	⬇️
web	51.93% <24.46%> (-0.10%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...ernal/config/dispatcher_resource_manager_config.go	35.29% <ø> (ø)
master/internal/config/resource_config.go	95.65% <100.00%> (+0.33%)	⬆️
master/internal/config/resource_pool_config.go	95.00% <ø> (ø)
master/internal/rm/kubernetesrm/request_queue.go	82.88% <100.00%> (+0.47%)	⬆️
master/internal/rm/kubernetesrm/spec.go	82.32% <100.00%> (+0.03%)	⬆️
master/internal/rm/rmerrors/errors.go	0.00% <ø> (ø)
webui/react/src/services/api.ts	97.75% <100.00%> (+0.05%)	⬆️
webui/react/src/types.ts	99.69% <100.00%> (+<0.01%)	⬆️
master/internal/rm/kubernetesrm/resource_pool.go	85.15% <95.65%> (+0.09%)	⬆️
master/internal/rm/resource_manager_iface.go	70.00% <0.00%> (-7.78%)	⬇️
... and 22 more

... and 22 files with indirect coverage changes

[amandavialva01]

...modals. OSS users can input a namespace to which they want to bind their workspace...

[tara-hpe]

lets merge these and they will get reviewed again when the release notes compilation happens

[amandavialva01]

WebUI:

• A new section called "Namespace Bindings" has been added to the Create Workspace and Edit Workspace modals. OSS users can input a namespace to which they want to bind their workspace for a given Kubernetes cluster. If no namespace is specified, the workspace will be bound to the namespace specified in the resource_manager.default_namespace field in the master configuration YAML. If this field is left blank, then the workspace will be bound to the default Kubernetes default namespace instead.
• MLDE users have the additional option of auto-creating a namespace to which the workspace will be bound. If this option is selected, users can also set a resource quota on that auto-created namespace. This will limit the GPU requests available to that workspace from a given Kubernetes cluster. The Edit Workspace Modal will display the enforced resource quota placed on the workspace, which is the lowest GPU limit resource quota that exists within the bound Kubernetes namespace.
• Once the workspace-namespace binding is saved, all workloads created in that workspace will be sent to the bound namespace. If a user decides to change their workspace-namespace binding, future workloads will get sent to the new namespace, but old workloads that are still in progress will remain running.

[tara-hpe]

since we do not use "OSS users" in our docs we'll just need to point out when a feature is for the enterprise edition. e.g., WebUI: In the enterprise edition, ...

(i.e., all users are OSS users and some users have the additional distinction of being Enterprise users > they get extra features)

[amandavialva01]

LGTM!

[tara-hpe]

LGTM