...
- We know it works and how to set it up (manually)
Cons:
- Obvious inscalabilityÂ
...
- Underlying Pods still rely on a pre-populated
hostPath, which feels wrong - This feels distinctly separate from the objective of deploying Kubernetes
Manually Create a PV and Bind
...
new PVC each time a new Namespace is Created
One way to get around the namespace-exclusivity of the PVC would be to create the PV ourselves.
...
- Workbench now needs to be PV-aware (Feels For some reason, it feels wrong to embed more PV/PVC logic here)
...
- Mountable across namespaces
Cons:
...
- Custom interface (NFS mounts) that will likely be unused elsewhere - seems annoying to need to support NFS mounting externally for one case
Run Workbench in a Single-Namespace
...
- Simplifies Workbench installation, makes it easier for users to understand (e.g. similar to JupyterHub, other related products)
- Mountable across namespaces
- PVC-friendly interface
- Close Closes a very old issue on GitHub: https://github.com/nds-org/ndslabs/issues/250
...