Integrating NORTH into OASIS
The goal is to make the NORTH tools available through the k8s infrastructure
Tasks:
-
tight the security for the containers of NORTH source By default we perform all logic for the abc user and we recommend using that user only in the container, but new users can be added as long as there is a startwm.sh executable script in their home directory. All of these containers are configured with passwordless sudo, we make no efforts to secure or harden these containers and we do not recommend ever publishing their ports to the public Internet.
-
revisit existing jupyterhub's docker spawner process -
adapt jupyterhub config file for k8s -
helm chart hierarchy (chart of charts / best practice) or integrate everything into the existing one -
gpu support for specific applications -
rebuild image (bypassing webtop) from baseimage -
configure ingress controller -
container isalive response (/healtz) -
container lifetime timeout? -
plans for docker image update cycle -
single vs separate repositories -
logging/monitoring -
update CI/CD pipeline -
testing, testing and testing -
.env file to store variables for docker compose -
building CLI tool for installation (enable/disable features/tools) -
improving on the documentation (eg. fixing links in the documentation)
Note: Please note that most probably some of the tasks mentioned above will have their own issue/branch but now everything is listed here