-
Story
-
Resolution: Done
-
Critical
-
RHODS_1.16.0_GA
-
False
-
False
-
devel-ack
-
Documentation (Ref Guide, User Guide, etc.)
-
No
-
-
-
-
-
-
1.16.0-5
-
No
-
Undefined
-
No
-
Yes
-
None
-
RHODS 1.16
This sub-task is to ensure we support the same core capability that's supported in JupyterHub via config maps, as this has been enabled for some customers (BU). The ability to define tolerations with specific container sizes will be covered in a separate story: RHODS-4735
Scope for this story:
- Want to enable customers to dedicate designated machine pools to notebook pods only.
- This should be an admin UI config option
Req:
- The system must allow RHODS admins to define tolerations for notebook pods via an admin UI.
Admins should be able to define multiple tolerations, as is possible in JH via config maps.
- clones
-
RHODS-1659 Support tolerations for Jupyter notebooks
- Closed
- is blocked by
-
RHODS-5001 Admin user can add unsupported toleration to notebook pods; spawning is impossible until toleration is changed
- Closed
- is duplicated by
-
RHODS-1659 Support tolerations for Jupyter notebooks
- Closed
- relates to
-
RHODS-2151 Replace JupyterHub with KF notebook controller - phase 0
- Closed
-
RHODS-5002 Subtext of toleration setting for RHODS admins is partially incorrect
- Closed
- links to
- mentioned on