-
Story
-
Resolution: Done
-
Critical
-
None
-
2
-
False
-
False
-
No
-
-
-
-
-
-
1.0.17
-
No
-
Undefined
-
No
-
Yes
-
None
-
-
IDH Sprint 3, IDH Sprint 4, IDH Sprint 5
In RHODS-280 we came up with a plan to deploy JupyterHub notebook pods into a dedicated namespace. Implement the plan. That plan is as follows:
- Decide on a name for the new namespace. Get Jeff DeMoss to approve the name. The namespace must not be prefixed with "redhat-"
- Add an entry to the list of namespaces created for the RHODS add-on for the new namespace (we will need to do this for integration, stage, and prod)
- Create a role binding granting the "jupyterhub-hub" service account in the redhat-ods-applications namespace permission to create pods and PVCs in the new namespace
- Customize the jupyterhub_config.py to override the namespace variable to be the new namespace
- Update jupyterhub_config.py to pass the new namespace to the SingleUserProfiles class
- Update the RHODS triage guide to include the new namespace in documentation.
- Update monitoring and alerting to ensure that everything works with the new namespace
- is blocked by
-
RHODS-280 [SPIKE] Come up with a plan to deploy individual JupyterHub notebook servers into a dedicated namespace
- Closed
- is documented by
-
RHODS-441 Document the architecture of OpenShift Data Science
- Closed
- is duplicated by
-
RHODS-823 [PLACEHOLDER] Implement plan to deploy JupyterHub notebook pods into separate namespace
- Closed