not sure if this is precisely what the questioner is after but will share anyhow. have developed something like this two times. both combine oss solutions with some custom tooling.
1. setup a platform using jupyterhub on kubernetes
* use case leans towards research and mixed research-dev workflows
* user only requires browser installed locally
* jupyterhub server selection menu is configured such that
* user selects container image to spawn from: these are usually built per project tool chain
* user selects node type to run on: for example if user needs gpu resources, then can schedule onto cluster node with gpu devices attached
2. setup a platform that integrates monorepo with vscode devcontainer
* use case focuses on developers
* requires vscode, docker installed locally
* monorepo contains a collection of subprojects for running services and jobs
* each subproject define its own devcontainer settings
* these follow common patterns per runtime and runtime version needed for project
* devcontainer images are pre-built and maintained in onprem container registry
1. setup a platform using jupyterhub on kubernetes * use case leans towards research and mixed research-dev workflows * user only requires browser installed locally * jupyterhub server selection menu is configured such that * user selects container image to spawn from: these are usually built per project tool chain * user selects node type to run on: for example if user needs gpu resources, then can schedule onto cluster node with gpu devices attached 2. setup a platform that integrates monorepo with vscode devcontainer * use case focuses on developers * requires vscode, docker installed locally * monorepo contains a collection of subprojects for running services and jobs * each subproject define its own devcontainer settings * these follow common patterns per runtime and runtime version needed for project * devcontainer images are pre-built and maintained in onprem container registry